Bitcoin Testnet Faucet

Weekly Update: 1 Million ParJar Tips,, SelfKey Mobile Wallet, Sentivate Social... – 6 Mar - 12 Mar'20

Weekly Update: 1 Million ParJar Tips,, SelfKey Mobile Wallet, Sentivate Social... – 6 Mar - 12 Mar'20
As Coronavirus (COVID-19) wreaks havoc across the world, we hope that Parachuters are safe, at home and healthy. This has been a difficult few months for everyone. But we will get over it. So let’s spread some good vibes with an update filled with awesome news from the Parachuteverse. Here’s your week at Parachute + partners (6 Mar - 12 Mar'20):

Starting off with a biggie. This week we crossed 1 million ParJar tips with a grand party in the Tiproom that left heads spinning and massive hangover. Haha! Click here for a sneak peek into the madness. Those who missed the party, woke up to 30k+ messages. And that happened within a couple of hours only. Wild! If that wasn’t enough, the TTR crew followed it up with a tiproom tipbattle with 6 teams (10 members each) fighting it out. Click here for the team lineups and rules. What ensued was a whirlwind comprising 80k+ tips. Double wild! LordHades shared the latest #FPL update according to which Novelcloud has now crossed LH to take second position. Alexis continues to be on top. If you’re already on BAGS token’s Dirty Bags platform, don’t forget to check out the Parachute posts over there. If you’re not on it yet, there’s $BAGS prizes for Parachuters who sign up. Bose’s random trivia in TTR got folks scratching their heads for answers.
A Gian food pic after ages. Though not cooked by him. Peruvian chicken. Yum!
Alejandro hosted a free-for-all CoD flash game in the Parachute War Zone followed by a battle royale. Congratulations to Clinton for being awarded the Bronze Seal of Transparency for his charity. GamrB0y’s trivia in TTR this week was based on science. Victor hosted a TTR quiz themed on MetaHumans. Charlotte’s math trivia was uber fun as always. Jobchain crew sponsored 750k $JOB as prizes for a round Robot Rise in the ParJar Gaming channel. Cap held a flash Parena this week. If you haven’t been keeping a tab on Parachute, you just missed on scoring some sweet $PAR. Like Achilleas almost did with his top prize. He won the finale but wasn't around to claim his 1st prize. So Bose snagged the winner’s spoils. But Cap being Cap made sure he didn’t miss out either. For Two-for-Tuesday this week, Gian got Parachuters to post music videos "featuring bands or songs that have a food or drink in their name". Like always, Sebastian was kind enough to compile a playlist with everyone’s posts. A flurry of beta testing activities related to Transak (fiat on/off ramp for ParJar) and swapping flung into action this week. For this week's #wholesomewed, Jason asked Parachuters "to draw a fierce non-existant creature that you would like as your champion in a parena".
What an amazing view Alexis!
In this week’s educational posts from aXpire, COO Matthew Markham wrote about the state of the legal tech market, the E-Billing industry, why legal billing software matters and artificial intelligence in law firm software. For the latest update video, click here. Still not sure what aXpire is all about? Check out their token overview and business presentation. The weekly 20k $AXPR token burn went ahead as per schedule. Insights from 2gether’s consumer report were published in a Cointelegraph article exploring women’s usage behaviour in crypto. For the full report on female users, click here. Euro deposits on the platform were briefly paused and subsequently restored because of a third party dependency. Upgrades were made to the $BTC transfer mechanism as well. But a high traffic issue led to a temporary stoppage of the crypto purchase feature. Birdchain released its 2 year roadmap. Few weeks back, we shared news of $BIRD being listed on Probit. CEO Joao Martins talked more about it in his video podcast this week. Probit also started a stake and earn event for $BIRD holders. Ethos’ parent company Voyager is now a sponsor of Scott Melker’s (The Wolf of All Streets) new podcast. For the latest Switch update, click here. Fantom announced the pre-launch of which will be an end-to-end DeFi suite of products. The project has been killing it on its socials. Want to see proof? Check out the social metric graph mapped by LunarCRUSH. Michael made a weekly update video to catch up on all the latest news. Click here to read the latest technical update. Fantom also announced its involvement in Fusion Protocol’s decentralised custodian solution DCRM Alliance.
Interesting insights from 2gether’s female crypto users report
The new XIO website layout and a new set of article were released this week. Zachary did a deep dive into the new stuff with a 40 minute video. For this week’s #XIOSocial discussions, Citizens talked about underrated qualities of successful entrepreneurs and about progressive decentralisation. DigiByte joined Uptrennd this week with their own community on the platform. Uptrennd crew marked the occasion with a cool giveaway. Looking to join the team? Don’t forget to apply for the open positions. How has the platform been fairing in the last 3 months vis-à-vis other platforms? Check out the numbers. Plus, congrats on crossing 70k members. YouTuber Chico Crypto joined Uptrennd this week. District0x’s weekly update covers news such as the new District Designer, latest Dapp Digest etc. Meme Factory launched a new contest. Hydro integrated Plaid’s account verification and aggregation services to its platform this week. This was followed by additional integrations with KYC provider Onfido and financial data provider MX. Silent Notary crew has created a new fund for pursuing IDL’s listing opportunities. Looking for human connections during the Coronavirus lockdown? OST’s Pepo app now has a dedicated community channel for this. SelfKey’s Mobile Wallet was launched this week. CoinLoan joined SelfKey’s crypto lending marketplace. Moreover, crypto exchange Bitkub was added to the exchange marketplace. Plus, the team compiled a list of data breaches at Facebook.
The new Crowdstaking graphic explains how it is different from crowdfunding
Realtime market widgets and downloads page were added to the Sentivate social site this week along with a ton of other upgrades. The beta test of the platform has also been a success on Windows and Mac. The browser build is ongoing with a naming contest to begin soon. If you have been keeping your eyes open, BAGS crew have been hosting some fun quizzes in the Dirty Bags channel for $BAGS prizes. Make sure to have a look when you have a moment. Last year, around this time, Pynk won the startup pitch competition at Wolves Summit. This week, CEO Seth Ward and COO Rupert Barksfield shared 8 tips for aspirants. The community also discussed about Facebook’s Libra Alliance this week. CyberFM started a special playlist on the Spotlight Channel to celebrate Women’s History Month. Harmony showcased its transaction speed and fees compared to Ethereum through a video demo. Plus, a fast finality demonstration. Click here to read last week’s #pow thread. If you would rather watch the video update, click here. Founder Stephen Tse shared some more updates over live videos (1, 2, 3, 4). And kudos for being the most active project on GitHub last week. The crew sat down with Vite Labs for a community AMA. The roadmap towards launching Open Staking was published. It is currently in the second phase out of four phases. Testers and hackers were welcomed to participate in Stake Heist - try and break the open staking design on the Pangaea testnet for 10M $ONE tokens in prizes.
The Sentivate social site community dashboard looks fresh!
Intellishare founder Raymond Xiong will sit down for a community AMA next week. Folks who sent in questions could win 50 $INE tokens as well. GET Protocol’s GUTS Tickets featured in a list of recommended portals for safe ticket purchases by the Netherlands’ Police. As part of its ticketing transparency standards documentation series, developer Kasper Keunen wrote about nodes this week. The $COTI conversion bridge has been reopened with some limits to ensure fair chance for everyone looking to convert from mainnet to ERC20/BEP2 tokens. For the latest newsletter, click here. The new COTI explorer was released as well. Apart from simple wallet-to-wallet transactions, it also tracks merchant txns, bridge txns etc. The dev team also released a detailed article explaining its multi-currency (MultiDAG) framework. For the token deployment demo, click here.

And with that, it’s a close for this week in Parachute! See you again soon. Bye!
submitted by abhijoysarkar to ParachuteToken [link] [comments]

Groestlcoin 6th Anniversary Release


Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.

Other Linux


Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here


ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.





ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.



Main Release (Main Net)
Testnet Release


ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.


Live Version (Not Recommended)



ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).





ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).




Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.


Remastered Improvements



ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.



Linux :
 pip3 install -r requirements.txt python3 bip39\ 


ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.



Linux / OSX (Instructions)


UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.



Main Net
Main Net (FDroid)
Test Net


UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.




UPDATED – P2Pool Test Net



Pre-Hosted Testnet P2Pool is available via


submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

⚡What is the Lightning Network? ⚡


Image Explanations:

Specifications / White Papers


Lightning Network Experts on Reddit

  • starkbot - (Elizabeth Stark - Lightning Labs)
  • roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • stile65 - (Alex Akselrod - Lightning Labs)
  • cfromknecht - (Conner Fromknecht - Lightning Labs)
  • RustyReddit - (Rusty Russell - Blockstream)
  • cdecker - (Christian Decker - Blockstream)
  • Dryja - (Tadge Dryja - Digital Currency Initiative)
  • josephpoon - (Joseph Poon)
  • fdrn - (Fabrice Drouin - ACINQ )
  • pmpadiou - (Pierre-Marie Padiou - ACINQ)

Lightning Network Experts on Twitter

  • @starkness - (Elizabeth Stark - Lightning Labs)
  • @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • @stile65 - (Alex Akselrod - Lightning Labs)
  • @bitconner - (Conner Fromknecht - Lightning Labs)
  • @johanth - (Johan Halseth - Lightning Labs)
  • @bvu - (Bryan Vu - Lightning Labs)
  • @rusty_twit - (Rusty Russell - Blockstream)
  • @snyke - (Christian Decker - Blockstream)
  • @JackMallers - (Jack Mallers - Zap)
  • @tdryja - (Tadge Dryja - Digital Currency Initiative)
  • @jcp - (Joseph Poon)
  • @alexbosworth - (Alex Bosworth -

Medium Posts

Learning Resources


Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

  • ZigZag - Disclaimer You must trust ZigZag to send to Target Address

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

  • LND - Lightning Network Daemon (Golang)
  • eclair - A Scala implementation of the Lightning Network (Scala)
  • c-lightning - A Lightning Network implementation in C
  • lit - Lightning Network node software (Golang)
  • lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
  • lightning-integration - Lightning Integration Testing Framework
  • ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]


Lightning Network Visualizers/Explorers



Payment Processors

  • BTCPay - Next stable version will include Lightning Network




Slack Channel

Discord Channel


⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
Bitcoin Stack Exchange Answer
What are Channel Factories and how do they work?
Bitcoin Stack Exchange Answer
How does the Lightning network work in simple terms?
Bitcoin Stack Exchange Answer
How are paths found in Lightning Network?
Bitcoin Stack Exchange Answer
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Stack Exchange Answer
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
No -- Source
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
Stack Exchange Answer
Can the Lightning Network work on any other cryptocurrency? How?
Stack Exchange Answer
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
Stack Exchange Answer

Unanswered Questions

How do on-chain fees work when opening and closing channels? Who pays the fee?
How does the Lightning Network work for mobile users?
What are the best practices for securing a lightning node?
What is a lightning "hub"?
How does lightning handle cross chain (Atomic) swaps?

Special Thanks and Notes

  • Many links found from awesome-lightning-network github
  • Everyone who submitted a question or concern!
  • I'm continuing to format for an easier Mobile experience!
submitted by codedaway to Bitcoin [link] [comments]

EOS - Getting Started & Helpful Links


Table of Contents

  1. What is EOS?
  2. Why is EOS Different?
  3. Get Started
  4. Channels, dApps, Block Explorer and more
    1. Governance and Security
    2. Wallets
    3. DApps
    4. Popular dApps
    5. Block Explorers
      1. REX User Interfaces
  5. Channels
  6. FAQ

What is EOS?

EOS is a community-driven distributed blockchain, that allows the development and execution of industrial-scale decentralized applications (dApps). Therefore, EOS intention is to become a blockchain dApp platform that can securely and smoothly scale to thousands of transactions per second, all while providing an accessible experience to app developers, entrepreneurs, and users. They aim to provide a complete operating system for decentralized applications by providing services like user authentication, cloud storage, and server hosting.
The EOS.IO open-source code was developed and it is currently updated by Block.One. Block.One is based in the Cayman Island and it is managed by Brendan Blumer (CEO), Daniel Larimer (CTO) and Andrew Bliss (CFO).

How is EOS different?

EOS is the first Blockchain that focuses on building a dApps platform by using the delegated proof-of-stake consensus mechanism. With dPoS, EOS manage to provide a public blockchain with some particular features, such as Scalability, Flexibility, Usability and Governance.
Further Reading:

Get Started:


From EOS Beginners: Anatomy of an EOS Account
An EOS account is a readable name that is stored on the EOS blockchain and connected to your “keys”. An EOS account is required for performing actions on the EOS platform, such as sending/receiving tokens, voting, and staking.
Each account is linked to a public key, and this public key is in turn linked to a private key. A private key can be used to generate an associated public key, but not vice versa. (A private key and its associated public key make up a key pair)
These keys ensure that only you can access and perform actions with your account. Your public key is visible by everyone using the network. Your private key, however, will never be shown. You must store your private keys in a safe location as they should not be shared with anyone (unless you want your EOS to be stolen)!
TLDR: EOS Accounts are controlled by key pairs and store EOS tokens in the Blockchain. Wallets store key pairs that are used to sign transactions.


From EOS Onboarding: Free Accounts
Unlike other chains in the space, EOSIO accounts do not typically charge a transfer fee for sending tokens or providing actions on the blockchain. Where Bitcoin and Ethereum mine blocks and charge a fee, EOS provides feeless transactions to users based on CPU, NET, and RAM resources.
Although traditionally those wanting to create EOS accounts in particular have needed to ‘pay a fee’ to get into the system, in reality this fee is nothing more than a basic stake of CPU and NET resources. In theory this provides free transactions on the network, the number of transactions that any user gets in a 24 hour window is determined by the amount of stake especially in CPU that any given account maintains.
This guide then provides a brief overview of the account creation process of some of those account types that allow for easy no friction EOS mainnet onboarding and in most cases, the provision of more than enough resources to be able to utilize the network without having to go through the process of buying, transferring, and staking or renting resources ensuring your account remains operational.


What is REX?
REX (Resource Exchange) is a resource market that can meet the demand, where the EOS token holders can lease out tokens in return for “rent”, and the Dapps can lease resources they need with less cost.
For EOS holders:Earn an income via put your spare EOS tokens in REX instead of just keep it on your EOS account.
For EOS Dapps:Lease as much resources as you need at a decent price instead of stake EOS for resources in 1:1 ratio.
Source: TokenPocket
Through REX you can pay a small amount of EOS to receive a much larger amount in CPU or NET for a whole month. Today (August 20, 2020), paying 1 EOS on REX guarantees you 7,500 EOS in CPU for 30 days.
You can easily use REX via Anchor Wallet, importing your EOS Account and with a few simple clicks. Learn how to use REX with Anchor


Decentralized Finance (DeFi) is the combination of traditional financial instruments with decentralized blockchain technology. Currently DeFi is the fastest growing sector in blockchain, which allows greater inclusion within the financial system even for those who previously could not participate in the global economy. Indeed, to use DeFi products is enough just a smartphone, and the so-called "unbanked", ca now participate without any restrictions.
DeFi Projects on EOS
  • VIGOR - VIGOR protocol is a borrow, lend, and save community
  • Defibox - One-stop EOS DeFi Platform
  • Equilibrium (EOSDT) - Equilibrium is an all-in-one Interoperable DeFi hub
  • [PredIQt]( - PredIQt is a prediction market & oracle protocol
  • PIZZA - PIZZA is an EOS based decentralized stablecoin system and financial platform
  • Chintai - high performance, fee-less community owned token leasing platform

Channels, dApps, Block Explorer and more

Governance and Security:



Popular dApps:

  • NewDex - Decentralized Exchange.
  • Prospectors -MMO Game with Real Time Economic Strategies
  • Everipedia - Wiki-based online encyclopedia
  • Upland - Property trading game with real-world addresses
  • Crypto Dynasty - Play-to-Earn with Crypto Dynasty

Block explorers:

Guides to vote:

REX User Interface:


Telegram Non-English General:


submitted by eosgo to eos [link] [comments]


With two cryptocurrency integrations under my belt I've set out with a solid plan for Monero.
Instead of jumping in and figuring it out as I go along I want to make sure that I have the solutions I'll need, well defined and scoped out. It's a good thing I'm going this path, too.
Turns out that there isn't really much in the way of JavaScript code for Monero out there. Probably the two best (and possibly only), solutions at the moment are monero-javascript and MyMonero.
Although there's no official Monero JavaScript library, the monero-javascript project is probably the closest to the original C++ client. This derived code comes in the form of WebAssembly, a low-level language that runs a lot closer to the metal than JavaScript. This means that WebAssembly is generally faster when doing things like calculations, but with some trade-offs like ease of use. JavaScript is a lot easier to code and understand, but it tends to run slower. In modern browsers, both run side by side so developers can decide which parts need to work fast, and which parts need to be easier to change and maintain.
The MyMonero project is actually a set of supporting libraries for a Monero wallet. It seems to have a lot more "real world" mileage but has a smaller dev team and hasn't been updated for many months, unlike monero-javascript which was updated as recently as today. MyMonero also uses WebAssembly for some of the core wallet functionality but the "bindings", or how this functionality is exposed to JavaScript, are different.
Between the two solutions, I've had more luck in getting support for monero-javascript. Neither project is well documented so having someone to run questions by is, at least at this point, a winning feature.
This will be my first time working with WebAssembly so factoring in some learning time is prudent. I'll only be learning to use existing code rather than learning how to write it but still, it's a new thing for me.
As I mentioned, support for Monero via JavaScript is surprisingly rare, so I may end up contributing some original code back to the project(s) I'll be using. I haven't yet decided which of them will find its way into CypherPoker.JS because there are still some open questions about how certain things are done and if they're even possible. However, right now monero-javascript is looking like the best choice.
Once I'm satisfied that all the building blocks are viable, I'll add the cryptocurrency handler and integrate it all the way through to the front end. As with BTC and BCH, a Monero testnet option will be available along with a faucet so that you can test it out without using any actual XMR. A full client option that uses the downloadable monerod client, the equivalent of a full Bitcoin node, will be available alongside the "light" option which will use external APIs. After that I'll upgrade the live demo (and server), update the wallet generator, post v0.5.2 code documentation, create a new release, and write a wrap-up post.
I want to stress again that this is all contingent on whether or not the JavaScript libraries actually do what I need them to do, and if there exists at least one public API that can be used in place of the daemon (monerod). But based on the help I've received from the Monero community so far I'm feeling optimistic.
Probably the most interesting thing about the Monero integration is that it represents the final, Rumsfeldian, "known unknown" of the CypherPoker.JS project. It's the last thing I'm embarking on with essentially zero prior knowledge; I know that I know nothing.
The rest of the project, the other cryptocurrencies, smart contracts, peer-to-peer communications - those are all things I'd at least had an introduction to if not outright practical knowledge of. When it comes time to add Ethereum support I'll be able to confidently say that it's nothing new. Incorporating Tor anonymization ... been there, done that.
When it comes to Monero, though, I'm a wide-eyed ignoramus. Never owned any XMR, never ran a Monero wallet, never tried out a Monero block explorer; seems I'm even getting some of the technical terminology wrong. Basically, it's the last part of the project's core vision that comes with a steep learning curve and a not-insignificant chance of failure. I mean, I don't think I'm gonna fail but I can't point to any definitive reason why I should think that.
There's no pragmatic reason to believe that March and (the) Monero (integration) will be contemporaneous but then again, why not?
submitted by monican_agent to cypherpoker [link] [comments]

12-22 13:34 - ' Etherscan Export CSV Data - 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-4699...' by /u/mahdiamolimoghadam removed from /r/Bitcoin within 128-138min

 Etherscan Export CSV Data - 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-46998878-6', { 'anonymize_ip': true }); .ether-search-heading { pointer-events: none !important; } .ether-search-heading .ui-menu-item-wrapper, .[link]^^1 .ui-menu-item-wrapper { cursor: default !important; border-color: transparent !important; 0 } .ui-menu-item .ether-search, .[link]^^2 .ether-search { background-color: transparent !important; border-color: #e7eaf3 !important; } .[link]^^2 .ether-search { background-color: #f8fafd !important; } .ui-menu-item .ether-search, .ui-menu-item .ether-search { background-color: transparent !important; border-color: transparent !important; } body.dark-mode .[link]^^2 .ether-search { background-color: #012137 !important; color: #a2b9c8 !important; border-color: #013558 !important; } //  Eth: $148.33 (-0.12%) Home Blockchain 
View Txns
View Pending Txns
View Contract Internal Txns
 View Blocks Forked Blocks (Reorgs) 
View Uncles
Top Accounts
Verified Contracts
ERC-20 Top Tokens
View ERC-20 Transfers
ERC-721 Top Tokens
View ERC-721 Transfers
Ethereum Directory
Charts & Stats
Top Statistics
 More Developers 
Verify Contract
Byte to Opcode
Broadcast TXN
Vyper Online Compiler
 Swarm & ENS 
SWARM Search
SWARM Upload
ENS Events
ENS Lookup
 Service Tracker 
Dapp Tracker New
DEX Tracker
DEX OrderBooks
Gas Tracker
Node Tracker
Loan Tracker
Mining Calculator
Verified Signature
Similiar Contracts
Label Word Cloud
 Sign In  Explorers 
Ethereum Mainnet
Ethereum Mainnet CN
Ropsten Testnet
Kovan Testnet
Rinkeby Testnet
Goerli Testnet
EWC Chain
Beacon Testnet Eth2.0
 All FiltersAddressesTokensName TagsLabelsWebsites 
Download Data (Transactions)
The information you requested can be downloaded from this page. But before continuing please verify that you are not a robot by completing the captcha below.
 Export the earliest 5000 records starting from  Powered by Ethereum 
Etherscan is a Block Explorer and Analytics Platform for Ethereum, a decentralized smart contracts platform.
About Us
Contact Us
Brand Assets
Terms of Service
Developer APIs
Knowledge Base
Network Status
Disqus Comments
Social Links
Etherscan آ© 2019 (A)
Donations 0x71c7656ec7ab88b098defb751b7401b5f6d8976f
 This website uses cookies to improve your experience and has an updated Privacy Policy. Got It $(window).on('load', function () { // initialization of HSMegaMenu component $('.js-mega-menu').HSMegaMenu({ event: 'hover', pageContainer: $('.container'), breakpoint: 767.98, hideTimeOut: 0 }); }); $(document).on('ready', function () { // initialization of header $.HSCore.components.HSHeader.init($('#header')); // initialization of unfold component $.HSCore.components.HSUnfold.init($('[data-unfold-target]'), { afterOpen: function () { $(this).find('input[type="search"]').focus(); } }); // initialization of malihu scrollbar $.HSCore.components.HSMalihuScrollBar.init($('.js-scrollbar')); // initialization of focus state $.HSCore.components.HSFocusState.init(); // initialization of go to $.HSCore.components.HSGoTo.init('.js-go-to'); // initialization of cubeportfolio //$.HSCore.components.HSCubeportfolio.init('.cbp'); }); var strGlobal = sessionStorage.getItem("ShowAs"); var cookieconsent = getCookie("etherscan_cookieconsent"); if (cookieconsent !== "True") { document.getElementById("divcookie").style.display = "block"; }; function getCookie(cname) { var name = cname + "="; var ca = document.cookie.split(';'); for (var i = 0; i < ca.length; i++) { var c = ca[i]; while (c.charAt(0) === ' ') { c = c.substring(1); } if (c.indexOf(name) === 0) { return c.substring(name.length, c.length); } } return ""; } $("#btnCookie").click(function () { $("#divcookie").fadeOut("slow", function () { var d = new Date(); d.setTime(d.getTime() + (1095 * 24 * 60 * 60 * 1000)); var expires = "expires=" + d.toUTCString(); document.cookie = "etherscan_cookieconsent=True" + ";" + expires + ";path=/";; }); }); function handleSearchText(data) { searchAddress = false; if ($("txtSearchInput").val() == "") { $("#hdnSearchText").val(""); } } jQuery(document).ready(function () { $.HSCore.components.HSRangeDatepicker.init('.js-range-datepicker'); $.HSCore.components.HSValidation.init('.js-validate'); }); var correctCaptcha = function (response) { //alert(response); }; function get_action(form) { var v = grecaptcha.getResponse(); if (v.length == 0) { console.log("You can't leave captcha code empty"); return false; } else { console.log("Captcha completed"); document.getElementById("responsetext").innerHTML = "
Your download is being processed.
"; document.getElementById("ContentPlaceHolder1_divAlertMsg").style.display = "none"; document.getElementById("ContentPlaceHolder1_btnSubmit").style.display = "none"; document.getElementById("rcaptcha").style.visibility = "hidden"; return true; } }
Context Link
Go1dfish undelete link
unreddit undelete link
Author: mahdiamolimoghadam
1: ether-search-heading:hover 2: ui-menu-item:hover 3: ui-menu-item:hover 4: ui-menu-item:hover
submitted by removalbot to removalbot [link] [comments]

Transcript of the community Q&A with Steve Shadders and Daniel Connolly of the Bitcoin SV development team. We talk about the path to big blocks, new opcodes, selfish mining, malleability, and why November will lead to a divergence in consensus rules. (Cont in comments)

We've gone through the painstaking process of transcribing the linked interview with Steve Shadders and Daniell Connolly of the Bitcoin SV team. There is an amazing amount of information in this interview that we feel is important for businesses and miners to hear, so we believe it was important to get this is a written form. To avoid any bias, the transcript is taken almost word for word from the video, with just a few changes made for easier reading. If you see any corrections that need to be made, please let us know.
Each question is in bold, and each question and response is timestamped accordingly. You can follow along with the video here:


Connor: 02:19.68,0:02:45.10
Alright so thank You Daniel and Steve for joining us. We're joined by Steve Shadders and Daniel Connolly from nChain and also the lead developers of the Satoshi’s Vision client. So Daniel and Steve do you guys just want to introduce yourselves before we kind of get started here - who are you guys and how did you get started?
Steve: 0,0:02:38.83,0:03:30.61
So I'm Steve Shadders and at nChain I am the director of solutions in engineering and specifically for Bitcoin SV I am the technical director of the project which means that I'm a bit less hands-on than Daniel but I handle a lot of the liaison with the miners - that's the conditional project.
Hi I’m Daniel I’m the lead developer for Bitcoin SV. As the team's grown that means that I do less actual coding myself but more organizing the team and organizing what we’re working on.
Connor 03:23.07,0:04:15.98
Great so we took some questions - we asked on Reddit to have people come and post their questions. We tried to take as many of those as we could and eliminate some of the duplicates, so we're gonna kind of go through each question one by one. We added some questions of our own in and we'll try and get through most of these if we can. So I think we just wanted to start out and ask, you know, Bitcoin Cash is a little bit over a year old now. Bitcoin itself is ten years old but in the past a little over a year now what has the process been like for you guys working with the multiple development teams and, you know, why is it important that the Satoshi’s vision client exists today?
Steve: 0:04:17.66,0:06:03.46
I mean yes well we’ve been in touch with the developer teams for quite some time - I think a bi-weekly meeting of Bitcoin Cash developers across all implementations started around November last year. I myself joined those in January or February of this year and Daniel a few months later. So we communicate with all of those teams and I think, you know, it's not been without its challenges. It's well known that there's a lot of disagreements around it, but some what I do look forward to in the near future is a day when the consensus issues themselves are all rather settled, and if we get to that point then there's not going to be much reason for the different developer teams to disagree on stuff. They might disagree on non-consensus related stuff but that's not the end of the world because, you know, Bitcoin Unlimited is free to go and implement whatever they want in the back end of a Bitcoin Unlimited and Bitcoin SV is free to do whatever they want in the backend, and if they interoperate on a non-consensus level great. If they don't not such a big problem there will obviously be bridges between the two, so, yeah I think going forward the complications of having so many personalities with wildly different ideas are going to get less and less.
Cory: 0:06:00.59,0:06:19.59
I guess moving forward now another question about the testnet - a lot of people on Reddit have been asking what the testing process for Bitcoin SV has been like, and if you guys plan on releasing any of those results from the testing?
Daniel: 0:06:19.59,0:07:55.55
Sure yeah so our release will be concentrated on the stability, right, with the first release of Bitcoin SV and that involved doing a large amount of additional testing particularly not so much at the unit test level but at the more system test so setting up test networks, performing tests, and making sure that the software behaved as we expected, right. Confirming the changes we made, making sure that there aren’t any other side effects. Because of, you know, it was quite a rush to release the first version so we've got our test results documented, but not in a way that we can really release them. We're thinking about doing that but we’re not there yet.
Steve: 0:07:50.25,0:09:50.87
Just to tidy that up - we've spent a lot of our time developing really robust test processes and the reporting is something that we can read on our internal systems easily, but we need to tidy that up to give it out for public release. The priority for us was making sure that the software was safe to use. We've established a test framework that involves a progression of code changes through multiple test environments - I think it's five different test environments before it gets the QA stamp of approval - and as for the question about the testnet, yeah, we've got four of them. We've got Testnet One and Testnet Two. A slightly different numbering scheme to the testnet three that everyone's probably used to – that’s just how we reference them internally. They're [1 and 2] both forks of Testnet Three. [Testnet] One we used for activation testing, so we would test things before and after activation - that one’s set to reset every couple of days. The other one [Testnet Two] was set to post activation so that we can test all of the consensus changes. The third one was a performance test network which I think most people have probably have heard us refer to before as Gigablock Testnet. I get my tongue tied every time I try to say that word so I've started calling it the Performance test network and I think we're planning on having two of those: one that we can just do our own stuff with and experiment without having to worry about external unknown factors going on and having other people joining it and doing stuff that we don't know about that affects our ability to baseline performance tests, but the other one (which I think might still be a work in progress so Daniel might be able to answer that one) is one of them where basically everyone will be able to join and they can try and mess stuff up as bad as they want.
Daniel: 0:09:45.02,0:10:20.93
Yeah, so we so we recently shared the details of Testnet One and Two with the with the other BCH developer groups. The Gigablock test network we've shared up with one group so far but yeah we're building it as Steve pointed out to be publicly accessible.
Connor: 0:10:18.88,0:10:44.00
I think that was my next question I saw that you posted on Twitter about the revived Gigablock testnet initiative and so it looked like blocks bigger than 32 megabytes were being mined and propagated there, but maybe the block explorers themselves were coming down - what does that revived Gigablock test initiative look like?
Daniel: 0:10:41.62,0:11:58.34
That's what did the Gigablock test network is. So the Gigablock test network was first set up by Bitcoin Unlimited with nChain’s help and they did some great work on that, and we wanted to revive it. So we wanted to bring it back and do some large-scale testing on it. It's a flexible network - at one point we had we had eight different large nodes spread across the globe, sort of mirroring the old one. Right now we scaled back because we're not using it at the moment so they'll notice I think three. We have produced some large blocks there and it's helped us a lot in our research and into the scaling capabilities of Bitcoin SV, so it's guided the work that the team’s been doing for the last month or two on the improvements that we need for scalability.
Steve: 0:11:56.48,0:13:34.25
I think that's actually a good point to kind of frame where our priorities have been in kind of two separate stages. I think, as Daniel mentioned before, because of the time constraints we kept the change set for the October 15 release as minimal as possible - it was just the consensus changes. We didn't do any work on performance at all and we put all our focus and energy into establishing the QA process and making sure that that change was safe and that was a good process for us to go through. It highlighted what we were missing in our team – we got our recruiters very busy recruiting of a Test Manager and more QA people. The second stage after that is performance related work which, as Daniel mentioned, the results of our performance testing fed into what tasks we were gonna start working on for the performance related stuff. Now that work is still in progress - some of the items that we identified the code is done and that's going through the QA process but it’s not quite there yet. That's basically the two-stage process that we've been through so far. We have a roadmap that goes further into the future that outlines more stuff, but primarily it’s been QA first, performance second. The performance enhancements are close and on the horizon but some of that work should be ongoing for quite some time.
Daniel: 0:13:37.49,0:14:35.14
Some of the changes we need for the performance are really quite large and really get down into the base level view of the software. There's kind of two groups of them mainly. One that are internal to the software – to Bitcoin SV itself - improving the way it works inside. And then there's other ones that interface it with the outside world. One of those in particular we're working closely with another group to make a compatible change - it's not consensus changing or anything like that - but having the same interface on multiple different implementations will be very helpful right, so we're working closely with them to make improvements for scalability.
Connor: 0:14:32.60,0:15:26.45
Obviously for Bitcoin SV one of the main things that you guys wanted to do that that some of the other developer groups weren't willing to do right now is to increase the maximum default block size to 128 megabytes. I kind of wanted to pick your brains a little bit about - a lot of the objection to either removing the box size entirely or increasing it on a larger scale is this idea of like the infinite block attack right and that kind of came through in a lot of the questions. What are your thoughts on the “infinite block attack” and is it is it something that that really exists, is it something that miners themselves should be more proactive on preventing, or I guess what are your thoughts on that attack that everyone says will happen if you uncap the block size?
Steve: 0:15:23.45,0:18:28.56
I'm often quoted on Twitter and Reddit - I've said before the infinite block attack is bullshit. Now, that's a statement that I suppose is easy to take out of context, but I think the 128 MB limit is something where there’s probably two schools of thought about. There are some people who think that you shouldn't increase the limit to 128 MB until the software can handle it, and there are others who think that it's fine to do it now so that the limit is increased when the software can handle it and you don’t run into the limit when this when the software improves and can handle it. Obviously we’re from the latter school of thought. As I said before we've got a bunch of performance increases, performance enhancements, in the pipeline. If we wait till May to increase the block size limit to 128 MB then those performance enhancements will go in, but we won't be able to actually demonstrate it on mainnet. As for the infinitive block attack itself, I mean there are a number of mitigations that you can put in place. I mean firstly, you know, going down to a bit of the tech detail - when you send a block message or send any peer to peer message there's a header which has the size of the message. If someone says they're sending you a 30MB message and you're receiving it and it gets to 33MB then obviously you know something's wrong so you can drop the connection. If someone sends you a message that's 129 MB and you know the block size limit is 128 you know it’s kind of pointless to download that message. So I mean these are just some of the mitigations that you can put in place. When I say the attack is bullshit, I mean I mean it is bullshit from the sense that it's really quite trivial to prevent it from happening. I think there is a bit of a school of thought in the Bitcoin world that if it's not in the software right now then it kind of doesn't exist. I disagree with that, because there are small changes that can be made to work around problems like this. One other aspect of the infinite block attack, and let’s not call it the infinite block attack, let's just call it the large block attack - it takes a lot of time to validate that we gotten around by having parallel pipelines for blocks to come in, so you've got a block that's coming in it's got a unknown stuck on it for two hours or whatever downloading and validating it. At some point another block is going to get mined b someone else and as long as those two blocks aren't stuck in a serial pipeline then you know the problem kind of goes away.
Cory: 0:18:26.55,0:18:48.27
Are there any concerns with the propagation of those larger blocks? Because there's a lot of questions around you know what the practical size of scaling right now Bitcoin SV could do and the concerns around propagating those blocks across the whole network.
Steve 0:18:45.84,0:21:37.73
Yes, there have been concerns raised about it. I think what people forget is that compact blocks and xThin exist, so if a 32MB block is not send 32MB of data in most cases, almost all cases. The concern here that I think I do find legitimate is the Great Firewall of China. Very early on in Bitcoin SV we started talking with miners on the other side of the firewall and that was one of their primary concerns. We had anecdotal reports of people who were having trouble getting a stable connection any faster than 200 kilobits per second and even with compact blocks you still need to get the transactions across the firewall. So we've done a lot of research into that - we tested our own links across the firewall, rather CoinGeeks links across the firewall as they’ve given us access to some of their servers so that we can play around, and we were able to get sustained rates of 50 to 90 megabits per second which pushes that problem quite a long way down the road into the future. I don't know the maths off the top of my head, but the size of the blocks that can sustain is pretty large. So we're looking at a couple of options - it may well be the chattiness of the peer-to-peer protocol causes some of these issues with the Great Firewall, so we have someone building a bridge concept/tool where you basically just have one kind of TX vacuum on either side of the firewall that collects them all up and sends them off every one or two seconds as a single big chunk to eliminate some of that chattiness. The other is we're looking at building a multiplexer that will sit and send stuff up to the peer-to-peer network on one side and send it over splitters, to send it over multiple links, reassemble it on the other side so we can sort of transition the great Firewall without too much trouble, but I mean getting back to the core of your question - yes there is a theoretical limit to block size propagation time and that's kind of where Moore's Law comes in. Putting faster links and you kick that can further down the road and you just keep on putting in faster links. I don't think 128 main blocks are going to be an issue though with the speed of the internet that we have nowadays.
Connor: 0:21:34.99,0:22:17.84
One of the other changes that you guys are introducing is increasing the max script size so I think right now it’s going from 201 to 500 [opcodes]. So I guess a few of the questions we got was I guess #1 like why not uncap it entirely - I think you guys said you ran into some concerns while testing that - and then #2 also specifically we had a question about how certain are you that there are no remaining n squared bugs or vulnerabilities left in script execution?
Steve: 0:22:15.50,0:25:36.79
It's interesting the decision - we were initially planning on removing that cap altogether and the next cap that comes into play after that (next effective cap is a 10,000 byte limit on the size of the script). We took a more conservative route and decided to wind that back to 500 - it's interesting that we got some criticism for that when the primary criticism I think that was leveled against us was it’s dangerous to increase that limit to unlimited. We did that because we’re being conservative. We did some research into these log n squared bugs, sorry – attacks, that people have referred to. We identified a few of them and we had a hard think about it and thought - look if we can find this many in a short time we can fix them all (the whack-a-mole approach) but it does suggest that there may well be more unknown ones. So we thought about putting, you know, taking the whack-a-mole approach, but that doesn't really give us any certainty. We will fix all of those individually but a more global approach is to make sure that if anyone does discover one of these scripts it doesn't bring the node to a screaming halt, so the problem here is because the Bitcoin node is essentially single-threaded, if you get one of these scripts that locks up the script engine for a long time everything that's behind it in the queue has to stop and wait. So what we wanted to do, and this is something we've got an engineer actively working on right now, is once that script validation goad path is properly paralyzed (parts of it already are), then we’ll basically assign a few threads for well-known transaction templates, and a few threads for any any type of script. So if you get a few scripts that are nasty and lock up a thread for a while that's not going to stop the node from working because you've got these other kind of lanes of the highway that are exclusively reserved for well-known script templates and they'll just keep on passing through. Once you've got that in place, and I think we're in a much better position to get rid of that limit entirely because the worst that's going to happen is your non-standard script pipelines get clogged up but everything else will keep keep ticking along - there are other mitigations for this as well I mean I know you could always put a time limit on script execution if they wanted to, and that would be something that would be up to individual miners. Bitcoin SV's job I think is to provide the tools for the miners and the miners can then choose, you know, how to make use of them - if they want to set time limits on script execution then that's a choice for them.
Daniel: 0:25:34.82,0:26:15.85
Yeah, I'd like to point out that a node here, when it receives a transaction through the peer to peer network, it doesn't have to accept that transaction, you can reject it. If it looks suspicious to the node it can just say you know we're not going to deal with that, or if it takes more than five minutes to execute, or more than a minute even, it can just abort and discard that transaction, right. The only time we can’t do that is when it's in a block already, but then it could decide to reject the block as well. It's all possibilities there could be in the software.
Steve: 0:26:13.08,0:26:20.64
Yeah, and if it's in a block already it means someone else was able to validate it so…
Cory: 0,0:26:21.21,0:26:43.60
There’s a lot of discussions about the re-enabled opcodes coming – OP_MUL, OP_INVERT, OP_LSHIFT, and OP_RSHIFT up invert op l shift and op r shift you maybe explain the significance of those op codes being re-enabled?
Steve: 0:26:42.01,0:28:17.01
Well I mean one of one of the most significant things is other than two, which are minor variants of DUP and MUL, they represent almost the complete set of original op codes. I think that's not necessarily a technical issue, but it's an important milestone. MUL is one that's that I've heard some interesting comments about. People ask me why are you putting OP_MUL back in if you're planning on changing them to big number operations instead of the 32-bit limit that they're currently imposed upon. The simple answer to that question is that we currently have all of the other arithmetic operations except for OP_MUL. We’ve got add divide, subtract, modulo – it’s odd to have a script system that's got all the mathematical primitives except for multiplication. The other answer to that question is that they're useful - we've talked about a Rabin signature solution that basically replicates the function of DATASIGVERIFY. That's just one example of a use case for this - most cryptographic primitive operations require mathematical operations and bit shifts are useful for a whole ton of things. So it's really just about completing that work and completing the script engine, or rather not completing it, but putting it back the way that it was it was meant to be.
Connor 0:28:20.42,0:29:22.62
Big Num vs 32 Bit. I've seen Daniel - I think I saw you answer this on Reddit a little while ago, but the new op codes using logical shifts and Satoshi’s version use arithmetic shifts - the general question that I think a lot of people keep bringing up is, maybe in a rhetorical way but they say why not restore it back to the way Satoshi had it exactly - what are the benefits of changing it now to operate a little bit differently?
Daniel: 0:29:18.75,0:31:12.15
Yeah there's two parts there - the big number one and the L shift being a logical shift instead of arithmetic. so when we re-enabled these opcodes we've looked at them carefully and have adjusted them slightly as we did in the past with OP_SPLIT. So the new LSHIFT and RSHIFT are bitwise operators. They can be used to implement arithmetic based shifts - I think I've posted a short script that did that, but we can't do it the other way around, right. You couldn't use an arithmetic shift operator to implement a bitwise one. It's because of the ordering of the bytes in the arithmetic values, so the values that represent numbers. The little endian which means they're swapped around to what many other systems - what I've considered normal - or big-endian. And if you start shifting that properly as a number then then shifting sequence in the bytes is a bit strange, so it couldn't go the other way around - you couldn't implement bitwise shift with arithmetic, so we chose to make them bitwise operators - that's what we proposed.
Steve: 0:31:10.57,0:31:51.51
That was essentially a decision that was actually made in May, or rather a consequence of decisions that were made in May. So in May we reintroduced OP_AND, OP_OR, and OP_XOR, and that was also another decision to replace three different string operators with OP_SPLIT was also made. So that was not a decision that we've made unilaterally, it was a decision that was made collectively with all of the BCH developers - well not all of them were actually in all of the meetings, but they were all invited.
Daniel: 0:31:48.24,0:32:23.13
Another example of that is that we originally proposed OP_2DIV and OP_2MUL was it, I think, and this is a single operator that multiplies the value by two, right, but it was pointed out that that can very easily be achieved by just doing multiply by two instead of having a separate operator for it, so we scrapped those, we took them back out, because we wanted to keep the number of operators minimum yeah.
Steve: 0:32:17.59,0:33:47.20
There was an appetite around for keeping the operators minimal. I mean the decision about the idea to replace OP_SUBSTR, OP_LEFT, OP_RIGHT with OP_SPLIT operator actually came from Gavin Andresen. He made a brief appearance in the Telegram workgroups while we were working out what to do with May opcodes and obviously Gavin's word kind of carries a lot of weight and we listen to him. But because we had chosen to implement the May opcodes (the bitwise opcodes) and treat the data as big-endian data streams (well, sorry big-endian not really applicable just plain data strings) it would have been completely inconsistent to implement LSHIFT and RSHIFT as integer operators because then you would have had a set of bitwise operators that operated on two different kinds of data, which would have just been nonsensical and very difficult for anyone to work with, so yeah. I mean it's a bit like P2SH - it wasn't a part of the original Satoshi protocol that once some things are done they're done and you know if you want to want to make forward progress you've got to work within that that framework that exists.
Daniel: 0:33:45.85,0:34:48.97
When we get to the big number ones then it gets really complicated, you know, number implementations because then you can't change the behavior of the existing opcodes, and I don't mean OP_MUL, I mean the other ones that have been there for a while. You can't suddenly make them big number ones without seriously looking at what scripts there might be out there and the impact of that change on those existing scripts, right. The other the other point is you don't know what scripts are out there because of P2SH - there could be scripts that you don't know the content of and you don't know what effect changing the behavior of these operators would mean. The big number thing is tricky, so another option might be, yeah, I don't know what the options for though it needs some serious thought.
Steve: 0:34:43.27,0:35:24.23
That’s something we've reached out to the other implementation teams about - actually really would like their input on the best ways to go about restoring big number operations. It has to be done extremely carefully and I don't know if we'll get there by May next year, or when, but we’re certainly willing to put a lot of resources into it and we're more than happy to work with BU or XT or whoever wants to work with us on getting that done and getting it done safely.
Connor: 0:35:19.30,0:35:57.49
Kind of along this similar vein, you know, Bitcoin Core introduced this concept of standard scripts, right - standard and non-standard scripts. I had pretty interesting conversation with Clemens Ley about use cases for “non-standard scripts” as they're called. I know at least one developer on Bitcoin ABC is very hesitant, or kind of pushed back on him about doing that and so what are your thoughts about non-standard scripts and the entirety of like an IsStandard check?
Steve: 0:35:58.31,0:37:35.73
I’d actually like to repurpose the concept. I think I mentioned before multi-threaded script validation and having some dedicated well-known script templates - when you say the word well-known script template there’s already a check in Bitcoin that kind of tells you if it's well-known or not and that's IsStandard. I'm generally in favor of getting rid of the notion of standard transactions, but it's actually a decision for miners, and it's really more of a behavioral change than it is a technical change. There's a whole bunch of configuration options that miners can set that affect what they do what they consider to be standard and not standard, but the reality is not too many miners are using those configuration options. So I mean standard transactions as a concept is meaningful to an arbitrary degree I suppose, but yeah I would like to make it easier for people to get non-standard scripts into Bitcoin so that they can experiment, and from discussions of I’ve had with CoinGeek they’re quite keen on making their miners accept, you know, at least initially a wider variety of transactions eventually.
Daniel: 0:37:32.85,0:38:07.95
So I think IsStandard will remain important within the implementation itself for efficiency purposes, right - you want to streamline base use case of cash payments through them and prioritizing. That's where it will remain important but on the interfaces from the node to the rest of the network, yeah I could easily see it being removed.
Cory: 0,0:38:06.24,0:38:35.46
*Connor mentioned that there's some people that disagree with Bitcoin SV and what they're doing - a lot of questions around, you know, why November? Why implement these changes in November - they think that maybe the six-month delay might not cause a split. Well, first off what do you think about the ideas of a potential split and I guess what is the urgency for November?
Steve: 0:38:33.30,0:40:42.42
Well in November there's going to be a divergence of consensus rules regardless of whether we implement these new op codes or not. Bitcoin ABC released their spec for the November Hard fork change I think on August 16th or 17th something like that and their client as well and it included CTOR and it included DSV. Now for the miners that commissioned the SV project, CTOR and DSV are controversial changes and once they're in they're in. They can't be reversed - I mean CTOR maybe you could reverse it at a later date, but DSV once someone's put a P2SH transaction into the project or even a non P2SH transaction in the blockchain using that opcode it's irreversible. So it's interesting that some people refer to the Bitcoin SV project as causing a split - we're not proposing to do anything that anyone disagrees with - there might be some contention about changing the opcode limit but what we're doing, I mean Bitcoin ABC already published their spec for May and it is our spec for the new opcodes, so in terms of urgency - should we wait? Well the fact is that we can't - come November you know it's bit like Segwit - once Segwit was in, yes you arguably could get it out by spending everyone's anyone can spend transactions but in reality it's never going to be that easy and it's going to cause a lot of economic disruption, so yeah that's it. We're putting out changes in because it's not gonna make a difference either way in terms of whether there's going to be a divergence of consensus rules - there's going to be a divergence whether whatever our changes are. Our changes are not controversial at all.
Daniel: 0:40:39.79,0:41:03.08
If we didn't include these changes in the November upgrade we'd be pushing ahead with a no-change, right, but the November upgrade is there so we should use it while we can. Adding these non-controversial changes to it.
Connor: 0:41:01.55,0:41:35.61
Can you talk about DATASIGVERIFY? What are your concerns with it? The general concept that's been kind of floated around because of Ryan Charles is the idea that it's a subsidy, right - that it takes a whole megabyte and kind of crunches that down and the computation time stays the same but maybe the cost is lesser - do you kind of share his view on that or what are your concerns with it?
Daniel: 0:41:34.01,0:43:38.41
Can I say one or two things about this – there’s different ways to look at that, right. I'm an engineer - my specialization is software, so the economics of it I hear different opinions. I trust some more than others but I am NOT an economist. I kind of agree with the ones with my limited expertise on that it's a subsidy it looks very much like it to me, but yeah that's not my area. What I can talk about is the software - so adding DSV adds really quite a lot of complexity to the code right, and it's a big change to add that. And what are we going to do - every time someone comes up with an idea we’re going to add a new opcode? How many opcodes are we going to add? I saw reports that Jihan was talking about hundreds of opcodes or something like that and it's like how big is this client going to become - how big is this node - is it going to have to handle every kind of weird opcode that that's out there? The software is just going to get unmanageable and DSV - that was my main consideration at the beginning was the, you know, if you can implement it in script you should do it, because that way it keeps the node software simple, it keeps it stable, and you know it's easier to test that it works properly and correctly. It's almost like adding (?) code from a microprocessor you know why would you do that if you can if you can implement it already in the script that is there.
Steve: 0:43:36.16,0:46:09.71
It’s actually an interesting inconsistency because when we were talking about adding the opcodes in May, the philosophy that seemed to drive the decisions that we were able to form a consensus around was to simplify and keep the opcodes as minimal as possible (ie where you could replicate a function by using a couple of primitive opcodes in combination, that was preferable to adding a new opcode that replaced) OP_SUBSTR is an interesting example - it's a combination of SPLIT, and SWAP and DROP opcodes to achieve it. So at really primitive script level we've got this philosophy of let's keep it minimal and at this sort of (?) philosophy it’s all let's just add a new opcode for every primitive function and Daniel's right - it's a question of opening the floodgates. Where does it end? If we're just going to go down this road, it almost opens up the argument why have a scripting language at all? Why not just add a hard code all of these functions in one at a time? You know, pay to public key hash is a well-known construct (?) and not bother executing a script at all but once we've done that we take away with all of the flexibility for people to innovate, so it's a philosophical difference, I think, but I think it's one where the position of keeping it simple does make sense. All of the primitives are there to do what people need to do. The things that people don't feel like they can't do are because of the limits that exist. If we had no opcode limit at all, if you could make a gigabyte transaction so a gigabyte script, then you can do any kind of crypto that you wanted even with 32-bit integer operations, Once you get rid of the 32-bit limit of course, a lot of those a lot of those scripts come up a lot smaller, so a Rabin signature script shrinks from 100MB to a couple hundred bytes.
Daniel: 0:46:06.77,0:47:36.65
I lost a good six months of my life diving into script, right. Once you start getting into the language and what it can do, it is really pretty impressive how much you can achieve within script. Bitcoin was designed, was released originally, with script. I mean it didn't have to be – it could just be instead of having a transaction with script you could have accounts and you could say trust, you know, so many BTC from this public key to this one - but that's not the way it was done. It was done using script, and script provides so many capabilities if you start exploring it properly. If you start really digging into what it can do, yeah, it's really amazing what you can do with script. I'm really looking forward to seeing some some very interesting applications from that. I mean it was Awemany his zero-conf script was really interesting, right. I mean it relies on DSV which is a problem (and some other things that I don't like about it), but him diving in and using script to solve this problem was really cool, it was really good to see that.
Steve: 0:47:32.78,0:48:16.44
I asked a question to a couple of people in our research team that have been working on the Rabin signature stuff this morning actually and I wasn't sure where they are up to with this, but they're actually working on a proof of concept (which I believe is pretty close to done) which is a Rabin signature script - it will use smaller signatures so that it can fit within the current limits, but it will be, you know, effectively the same algorithm (as DSV) so I can't give you an exact date on when that will happen, but it looks like we'll have a Rabin signature in the blockchain soon (a mini-Rabin signature).
Cory: 0:48:13.61,0:48:57.63
Based on your responses I think I kinda already know the answer to this question, but there's a lot of questions about ending experimentation on Bitcoin. I was gonna kind of turn that into – with the plan that Bitcoin SV is on do you guys see like a potential one final release, you know that there's gonna be no new opcodes ever released (like maybe five years down the road we just solidify the base protocol and move forward with that) or are you guys more on the idea of being open-ended with appropriate testing that we can introduce new opcodes under appropriate testing.
Steve: 0:48:55.80,0:49:47.43
I think you've got a factor in what I said before about the philosophical differences. I think new functionality can be introduced just fine. Having said that - yes there is a place for new opcodes but it's probably a limited place and in my opinion the cryptographic primitive functions for example CHECKSIG uses ECDSA with a specific elliptic curve, hash 256 uses SHA256 - at some point in the future those are going to no longer be as secure as we would like them to be and we'll replace them with different hash functions, verification functions, at some point, but I think that's a long way down the track.
Daniel: 0:49:42.47,0:50:30.3
I'd like to see more data too. I'd like to see evidence that these things are needed, and the way I could imagine that happening is that, you know, that with the full scripting language some solution is implemented and we discover that this is really useful, and over a period of, like, you know measured in years not days, we find a lot of transactions are using this feature, then maybe, you know, maybe we should look at introducing an opcode to optimize it, but optimizing before we even know if it's going to be useful, yeah, that's the wrong approach.
Steve: 0:50:28.19,0:51:45.29
I think that optimization is actually going to become an economic decision for the miners. From the miner’s point of view is if it'll make more sense for them to be able to optimize a particular process - does it reduce costs for them such that they can offer a better service to everyone else? Yeah, so ultimately these decisions are going to be miner’s main decisions, not developer decisions. Developers of course can offer their input - I wouldn't expect every miner to be an expert on script, but as we're already seeing miners are actually starting to employ their own developers. I’m not just talking about us - there are other miners in China that I know have got some really bright people on their staff that question and challenge all of the changes - study them and produce their own reports. We've been lucky with actually being able to talk to some of those people and have some really fascinating technical discussions with them.
submitted by The_BCH_Boys to btc [link] [comments]

Please help me test my Lightning wallet

I've released a testnet version of Android Lightning wallet today, would very much appreciate if you could help me with testing by trying it out.
Google Play: Direct APK download:
Project website
Bug reporting
Places where you can spend Lightning funds
Recommended nodes to connect to (they are hosted on a dedicated servers and are thus more reliable)
Lightning wallet details
I've made a couple of videos you might be interested in
submitted by akumaigorodski to Bitcoin [link] [comments]

Your Guide to Monero, and Why It Has Great Potential

/////Your Guide to Monero, and Why It Has Great Potential/////

It's a dirty word for most members of the Monero community.
It is also one of the most divisive words in the Monero community. Yet, the lack of marketing is one of the most frustrating things for many newcomers.
This is what makes this an unusual post from a member of the Monero community.
This post is an unabashed and unsolicited analyzation of why I believe Monero to have great potential.
Below I have attempted to outline different reasons why Monero has great potential, beginning with upcoming developments and use cases, to broader economic motives, speculation, and key issues for it to overcome.
I encourage you to discuss and criticise my musings, commenting below if you feel necessary to do so.

///Upcoming Developments///

Bulletproofs - A Reduction in Transaction Sizes and Fees
Since the introduction of Ring Confidential Transactions (Ring CT), transaction amounts have been hidden in Monero, albeit at the cost of increased transaction fees and sizes. In order to mitigate this issue, Bulletproofs will soon be added to reduce both fees and transaction size by 80% to 90%. This is great news for those transacting smaller USD amounts as people commonly complained Monero's fees were too high! Not any longer though! More information can be found here. Bulletproofs are already working on the Monero testnet, and developers were aiming to introduce them in March 2018, however it could be delayed in order to ensure everything is tried and tested.
Multisig has recently been merged! Mulitsig, also called multisignature, is the requirement for a transaction to have two or more signatures before it can be executed. Multisig transactions and addresses are indistinguishable from normal transactions and addresses in Monero, and provide more security than single-signature transactions. It is believed this will lead to additional marketplaces and exchanges to supporting Monero.
Kovri is an implementation of the Invisible Internet Project (I2P) network. Kovri uses both garlic encryption and garlic routing to create a private, protected overlay-network across the internet. This overlay-network provides users with the ability to effectively hide their geographical location and internet IP address. The good news is Kovri is under heavy development and will be available soon. Unlike other coins' false privacy claims, Kovri is a game changer as it will further elevate Monero as the king of privacy.
Mobile Wallets
There is already a working Android Wallet called Monerujo available in the Google Play Store. X Wallet is an IOS mobile wallet. One of the X Wallet developers recently announced they are very, very close to being listed in the Apple App Store, however are having some issues with getting it approved. The official Monero IOS and Android wallets, along with the MyMonero IOS and Android wallets, are also almost ready to be released, and can be expected very soon.
Hardware Wallets
Hardware wallets are currently being developed and nearing completion. Because Monero is based on the CryptoNote protocol, it means it requires unique development in order to allow hardware wallet integration. The Ledger Nano S will be adding Monero support by the end of Q1 2018. There is a recent update here too. Even better, for the first time ever in cryptocurrency history, the Monero community banded together to fund the development of an exclusive Monero Hardware Wallet, and will be available in Q2 2018, costing only about $20! In addition, the CEO of Trezor has offered a 10BTC bounty to whoever can provide the software to allow Monero integration. Someone can be seen to already be working on that here.
TAILS Operating System Integration
Monero is in the progress of being packaged in order for it to be integrated into TAILS and ready to use upon install. TAILS is the operating system popularised by Edward Snowden and is commonly used by those requiring privacy such as journalists wanting to protect themselves and sources, human-right defenders organizing in repressive contexts, citizens facing national emergencies, domestic violence survivors escaping from their abusers, and consequently, darknet market users.
In the meantime, for those users who wish to use TAILS with Monero, u/Electric_sheep01 has provided Sheep's Noob guide to Monero GUI in Tails 3.2, which is a step-by-step guide with screenshots explaining how to setup Monero in TAILS, and is very easy to follow.
Mandatory Hardforks
Unlike other coins, Monero receives a protocol upgrade every 6 months in March and September. Think of it as a Consensus Protocol Update. Monero's hard forks ensure quality development takes place, while preventing political or ideological issues from hindering progress. When a hardfork occurs, you simply download and use the new daemon version, and your existing wallet files and copy of the blockchain remain compatible. This reddit post provides more information.
Dynamic fees
Many cryptocurrencies have an arbitrary block size limit. Although Monero has a limit, it is adaptive based on the past 100 blocks. Similarly, fees change based on transaction volume. As more transactions are processed on the Monero network, the block size limit slowly increases and the fees slowly decrease. The opposite effect also holds true. This means that the more transactions that take place, the cheaper the fees!
Tail Emission and Inflation
There will be around 18.4 million Monero mined at the end of May 2022. However, tail emission will kick in after that which is 0.6 XMR, so it has no fixed limit. Gundamlancer explains that Monero's "main emission curve will issue about 18.4 million coins to be mined in approximately 8 years. (more precisely 18.132 Million coins by ca. end of May 2022) After that, a constant "tail emission" of 0.6 XMR per 2-minutes block (modified from initially equivalent 0.3 XMR per 1-minute block) will create a sub-1% perpetual inflatio starting with 0.87% yearly inflation around May 2022) to prevent the lack of incentives for miners once a currency is not mineable anymore.
Monero Research Lab
Monero has a group of anonymous/pseudo-anonymous university academics actively researching, developing, and publishing academic papers in order to improve Monero. See here and here. The Monero Research Lab are acquainted with other members of cryptocurrency academic community to ensure when new research or technology is uncovered, it can be reviewed and decided upon whether it would be beneficial to Monero. This ensures Monero will always remain a leading cryptocurrency. A recent end of 2017 update from a MRL researcher can be found here.

///Monero's Technology - Rising Above The Rest///

Monero Has Already Proven Itself To Be Private, Secure, Untraceable, and Trustless
Monero is the only private, untraceable, trustless, secure and fungible cryptocurrency. Bitcoin and other cryptocurrencies are TRACEABLE through the use of blockchain analytics, and has lead to the prosecution of numerous individuals, such as the alleged Alphabay administrator Alexandre Cazes. In the Forfeiture Complaint which detailed the asset seizure of Alexandre Cazes, the anonymity capabilities of Monero were self-demonstrated by the following statement of the officials after the AlphaBay shutdown: "In total, from CAZES' wallets and computer agents took control of approximately $8,800,000 in Bitcoin, Ethereum, Monero and Zcash, broken down as follows: 1,605.0503851 Bitcoin, 8,309.271639 Ethereum, 3,691.98 Zcash, and an unknown amount of Monero".
Privacy CANNOT BE OPTIONAL and must be at a PROTOCOL LEVEL. With Monero, privacy is mandatory, so that everyone gets the benefits of privacy without any transactions standing out as suspicious. This is the reason Darknet Market places are moving to Monero, and will never use Verge, Zcash, Dash, Pivx, Sumo, Spectre, Hush or any other coins that lack good privacy. Peter Todd (who was involved in the Zcash trusted setup ceremony) recently reiterated his concerns of optional privacy after Jeffrey Quesnelle published his recent paper stating 31.5% of Zcash transactions may be traceable, and that only ~1% of the transactions are pure privacy transactions (i.e., z -> z transactions). When the attempted private transactions stand out like a sore thumb there is no privacy, hence why privacy cannot be optional. In addition, in order for a cryptocurrency to truly be private, it must not be controlled by a centralised body, such as a company or organisation, because it opens it up to government control and restrictions. This is no joke, but Zcash is supported by DARPA and the Israeli government!.
Monero provides a stark contrast compared to other supposed privacy coins, in that Monero does not have a rich list! With all other coins, you can view wallet balances on the blockexplorers. You can view Monero's non-existent rich list here to see for yourself.
I will reiterate here that Monero is TRUSTLESS. You don't need to rely on anyone else to protect your privacy, or worry about others colluding to learn more about you. No one can censor your transaction or decide to intervene. Monero is immutable, unlike Zcash, in which the lead developer Zooko publicly tweeted the possibility of providing a backdoor for authorities to trace transactions. To Zcash's demise, Zooko famously tweeted:
" And by the way, I think we can successfully make Zcash too traceable for criminals like WannaCry, but still completely private & fungible. …"
Ethereum's track record of immutability is also poor. Ethereum was supposed to be an immutable blockchain ledger, however after the DAO hack this proved to not be the case. A 2016 article on Saintly Law summarised the problematic nature of Ethereum's leadership and blockchain intervention:
" Many ethereum and blockchain advocates believe that the intervention was the wrong move to make in this situation. Smart contracts are meant to be self-executing, immutable and free from disturbance by organisations and intermediaries. Yet the building block of all smart contracts, the code, is inherently imperfect. This means that the technology is vulnerable to the same malicious hackers that are targeting businesses and governments. It is also clear that the large scale intervention after the DAO hack could not and would not likely be taken in smaller transactions, as they greatly undermine the viability of the cryptocurrency and the technology."
Monero provides Fungibility and Privacy in a Cashless World
As outlined on, fungibility is the property of a currency whereby two units can be substituted in place of one another. Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR. Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation coinbase transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the blockchain in perpetuity.
A great example of Bitcoin's lack of fungibility was reposted by u/ViolentlyPeaceful:
"Imagine you sell cupcakes and receive Bitcoin as payment. It turns out that someone who owned that Bitcoin before you was involved in criminal activity. Now you are worried that you have become a suspect in a criminal case, because the movement of funds to you is a matter of public record. You are also worried that certain Bitcoins that you thought you owned will be considered ‘tainted’ and that others will refuse to accept them as payment."
This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies. Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
The world is moving cashless. Fact. The ramifications of this are enormous as we move into a cashless world in which transactions will be tracked and there is a potential for data to be used by third parties for adverse purposes. While most new cryptocurrency investors speculate upon vaporware ICO tokens in the hope of generating wealth, Monero provides salvation for those in which financial privacy is paramount. Too often people equate Monero's features with criminal endeavors. Privacy is not a crime, and is necessary for good money. Transparency in Monero is possible OFF-CHAIN, which offers greater transparency and flexibility. For example, a Monero user may share their Private View Key with their accountant for tax purposes.
Monero aims to be adopted by more than just those with nefarious use cases. For example, if you lived in an oppressive religious regime and wanted to buy a certain item, using Monero would allow you to exchange value privately and across borders if needed. Another example is that if everybody can see how much cryptocurrency you have in your wallet, then a certain service might decide to charge you more, and bad actors could even use knowledge of your wallet balance to target you for extortion purposes. For example, a Russian cryptocurrency blogger was recently beaten and robbed of $425k. This is why FUNGIBILITY IS ESSENTIAL. To summarise this in a nutshell:
"A lack of fungibility means that when sending or receiving funds, if the other person personally knows you during a transaction, or can get any sort of information on you, or if you provide a residential address for shipping etc. – you could quite potentially have them use this against you for personal gain"
For those that wish to seek more information about why Monero is a superior form of money, read The Merits of Monero: Why Monero Vs Bitcoin over on the website.
Monero's Humble Origins
Something that still rings true today despite the great influx of money into cryptocurrencies was outlined in Nick Tomaino's early 2016 opinion piece. The author claimed that "one of the most interesting aspects of Monero is that the project has gained traction without a crowd sale pre-launch, without VC funding and any company or well-known investors and without a pre-mine. Like Bitcoin in the early days, Monero has been a purely grassroots movement that was bootstrapped by the creator and adopted organically without any institutional buy-in. The creator and most of the core developers serve the community pseudonymously and the project was launched on a message board (similar to the way Bitcoin was launched on an email newsletter)."
The Organic Growth of the Monero Community
The Monero community over at monero is exponentially growing. You can view the Monero reddit metrics here and see that the Monero subreddit currently gains more than 10,000 (yes, ten thousand!) new subscribers every 10 days! Compare this to most of the other coins out there, and it proves to be one of the only projects with real organic growth. In addition to this, the community subreddits are specifically divided to ensure the main subreddit remains unbiased, tech focused, with no shilling or hype. All trading talk is designated to xmrtrader, and all memes at moonero.
Forum Funding System
While most contributors have gratefully volunteered their time to the project, Monero also has a Forum Funding System in which money is donated by community members to ensure it attracts and retains the brightest minds and most skilled developers. Unlike ICOs and other cryptocurrencies, Monero never had a premine, and does not have a developer tax. If ANYONE requires funding for a Monero related project, then they can simply request funding from the community, and if the community sees it as beneficial, they will donate. Types of projects range from Monero funding for local meet ups, to paying developers for their work.
Monero For Goods, Services, and Market Places
There is a growing number of online goods and services that you can now pay for with Monero. Globee is a service that allows online merchants to accept payments through credit cards and a host of cryptocurrencies, while being settled in Bitcoin, Monero or fiat currency. Merchants can reach a wider variety of customers, while not needing to invest in additional hardware to run cryptocurrency wallets or accept the current instability of the cryptocurrency market. Globee uses all of the open source API's that BitPay does making integrations much easier!
Project Coral Reef is a service which allows you to shop and pay for popular music band products and services using Monero.
Linux, Veracrypt, and a whole array of VPNs now accept Monero.
There is a new Monero only marketplace called Annularis currently being developed which has been created for those who value financial privacy and economic freedom, and there are rumours Open Bazaar is likely to support Monero once Multisig is implemented.
In addition, Monero is also supported by The Living Room of Satoshi so you can pay bills or credit cards directly using Monero.
Monero can be found on a growing number of cryptocurrency exchange services such as Bittrex, Poloniex, Cryptopia, Shapeshift, Changelly, Bitfinex, Kraken, Bisq, Tux, and many others.
For those wishing to purchase Monero anonymously, there are services such as and
With XMR.TO you can pay Bitcoin addresses directly with Monero. There are no other fees than the miner ones. All user records are purged after 48 hours. XMR.TO has also been added as an embedded feature into the Monerujo android wallet.
Coinhive Browser-Based Mining
Unlike Bitcoin, Monero can be mined using CPUs and GPUs. Not only does this encourage decentralisation, it also opens the door to browser based mining. Enter side of stage, Coinhive browser-based mining. As described by Hon Lau on the Symnatec Blog Browser-based mining, as its name suggests, is a method of cryptocurrency mining that happens inside a browser and is implemented using Javascript. Coinhive is marketed as an alternative to browser ad revenue. The motivation behind this is simple: users pay for the content indirectly by coin mining when they visit the site and website owners don't have to bother users with sites laden with ads, trackers, and all the associated paraphern. This is great, provided that the websites are transparent with site visitors and notify users of the mining that will be taking place, or better still, offer users a way to opt in, although this hasn't always been the case thus far.
Skepticism Sunday
The main Monero subreddit has weekly Skepticism Sundays which was created with the purpose of installing "a culture of being scientific, skeptical, and rational". This is used to have open, critical discussions about monero as a technology, it's economics, and so on.


Major Investors And Crypto Figureheads Are Interested
Ari Paul is the co-founder and CIO of BlockTower Capital. He was previously a portfolio manager for the University of Chicago's $8 billion endowment, and a derivatives market maker and proprietary trader for Susquehanna International Group. Paul was interviewed on CNBC on the 26th of December and when asked what was his favourite coin was, he stated "One that has real fundamental value besides from Bitcoin is Monero" and said it has "very strong engineering". In addition, when he was asked if that was the one used by criminals, he replied "Everything is used by criminals including the US dollar and the Euro". Paul later supported these claims on Twitter, recommending only Bitcoin and Monero as long-term investments.
There are reports that "Roger Ver, earlier known as 'Bitcoin Jesus' for his evangelical support of the Bitcoin during its early years, said his investment in Monero is 'substantial' and his biggest in any virtual currency since Bitcoin.
Charlie Lee, the creator of Litecoin, has publicly stated his appreciation of Monero. In a September 2017 tweet directed to Edward Snowden explaining why Monero is superior to Zcash, Charlie Lee tweeted:
All private transactions, More tested privacy tech, No tax on miners to pay investors, No high inflation... better investment.
John McAfee, arguably cryptocurrency's most controversial character at the moment, has publicly supported Monero numerous times over the last twelve months(before he started shilling ICOs), and has even claimed it will overtake Bitcoin.
Playboy instagram celebrity Dan Bilzerian is a Monero investor, with 15% of his portfolio made up of Monero.
Finally, while he may not be considered a major investor or figurehead, Erik Finman, a young early Bitcoin investor and multimillionaire, recently appeared in a CNBC Crypto video interview, explaining why he isn't entirely sold on Bitcoin anymore, and expresses his interest in Monero, stating:
"Monero is a really good one. Monero is an incredible currency, it's completely private."
There is a common belief that most of the money in cryptocurrency is still chasing the quick pump and dumps, however as the market matures, more money will flow into legitimate projects such as Monero. Monero's organic growth in price is evidence smart money is aware of Monero and gradually filtering in.
The Bitcoin Flaw
A relatively unknown blogger named CryptoIzzy posted three poignant pieces regarding Monero and its place in the world. The Bitcoin Flaw: Monero Rising provides an intellectual comparison of Monero to other cryptocurrencies, and Valuing Cryptocurrencies: An Approach outlines methods of valuing different coins.
CryptoIzzy's most recent blog published only yesterday titled Monero Valuation - Update and Refocus is a highly recommended read. It touches on why Monero is much more than just a coin for the Darknet Markets, and provides a calculated future price of Monero.
CryptoIzzy also published The Power of Money: A Case for Bitcoin, which is an exploration of our monetary system, and the impact decentralised cryptocurrencies such as Bitcoin and Monero will have on the world. In the epilogue the author also provides a positive and detailed future valuation based on empirical evidence. CryptoIzzy predicts Monero to easily progress well into the four figure range.
Monero Has a Relatively Small Marketcap
Recently we have witnessed many newcomers to cryptocurrency neglecting to take into account coins' marketcap and circulating supply, blindly throwing money at coins under $5 with inflated marketcaps and large circulating supplies, and then believing it's possible for them to reach $100 because someone posted about it on Facebook or Reddit.
Compared to other cryptocurrencies, Monero still has a low marketcap, which means there is great potential for the price to multiply. At the time of writing, according to CoinMarketCap, Monero's marketcap is only a little over $5 billion, with a circulating supply of 15.6 million Monero, at a price of $322 per coin.
For this reason, I would argue that this is evidence Monero is grossly undervalued. Just a few billion dollars of new money invested in Monero can cause significant price increases. Monero's marketcap only needs to increase to ~$16 billion and the price will triple to over $1000. If Monero's marketcap simply reached ~$35 billion (just over half of Ripple's $55 billion marketcap), Monero's price will increase 600% to over $2000 per coin.
Another way of looking at this is Monero's marketcap only requires ~$30 billion of new investor money to see the price per Monero reach $2000, while for Ethereum to reach $2000, Ethereum's marketcap requires a whopping ~$100 billion of new investor money.
Technical Analysis
There are numerous Monero technical analysts, however none more eerily on point than the crowd-pleasing Ero23. Ero23's charts and analysis can be found on Trading View. Ero23 gained notoriety for his long-term Bitcoin bull chart published in February, which is still in play today. Head over to his Trading View page to see his chart: Monero's dwindling supply. $10k in 2019 scenario, in which Ero23 predicts Monero to reach $10,000 in 2019. There is also this chart which appears to be freakishly accurate and is tracking along perfectly today.
Coinbase Rumours
Over the past 12 months there have been ongoing rumours that Monero will be one of the next cryptocurrencies to be added to Coinbase. In January 2017, Monero Core team member Riccardo 'Fluffypony' Spagni presented a talk at Coinbase HQ. In addition, in November 2017 GDAX announced the GDAX Digit Asset Framework outlining specific parameters cryptocurrencies must meet in order to be added to the exchange. There is speculation that when Monero has numerous mobile and hardware wallets available, and multisig is working, then it will be added. This would enable public accessibility to Monero to increase dramatically as Coinbase had in excess of 13 million users as of December, and is only going to grow as demand for cryptocurrencies increases. Many users argue that due to KYC/AML regulations, Coinbase will never be able to add Monero, however the Kraken exchange already operates in the US and has XMfiat pairs, so this is unlikely to be the reason Coinbase is yet to implement XMfiat trading.
Monero Is Not an ICO Scam
It is likely most of the ICOs which newcomers invest in, hoping to get rich quick, won't even be in the Top 100 cryptocurrencies next year. A large portion are most likely to be pumps and dumps, and we have already seen numerous instances of ICO exit scams. Once an ICO raises millions of dollars, the developers or CEO of the company have little incentive to bother rolling out their product or service when they can just cash out and leave. The majority of people who create a company to provide a service or product, do so in order to generate wealth. Unless these developers and CEOs are committed and believed in their product or service, it's likely that the funds raised during the ICO will far exceed any revenue generated from real world use cases.
Monero is a Working Currency, Today
Monero is a working currency, here today.
The majority of so called cryptocurrencies that exist today are not true currencies, and do not aim to be. They are a token of exchange. They are like a share in a start-up company hoping to use blockchain technology to succeed in business. A crypto-assest is a more accurate name for coins such as Ethereum, Neo, Cardano, Vechain, etc.
Monero isn't just a vaporware ICO token that promises to provide a blockchain service in the future. It is not a platform for apps. It is not a pump and dump coin.
Monero is the only coin with all the necessary properties to be called true money.
Monero is private internet money.
Some even describe Monero as an online Swiss Bank Account or Bitcoin 2.0, and it is here to continue on from Bitcoin's legacy.
Monero is alleviating the public from the grips of banks, and protests the monetary system forced upon us.
Monero only achieved this because it is the heart and soul, and blood, sweat, and tears of the contributors to this project. Monero supporters are passionate, and Monero has gotten to where it is today thanks to its contributors and users.

///Key Issues for Monero to Overcome///

While Bulletproofs are soon to be implemented in order to improve Monero's transaction sizes and fees, scalability is an issue for Monero that is continuously being assessed by Monero's researchers and developers to find the most appropriate solution. Ricardo 'Fluffypony' Spagni recently appeared on CNBC's Crypto Trader, and when asked whether Monero is scalable as it stands today, Spagni stated that presently, Monero's on-chain scaling is horrible and transactions are larger than Bitcoin's (because of Monero's privacy features), so side-chain scaling may be more efficient. Spagni elaborated that the Monero team is, and will always be, looking for solutions to an array of different on-chain and off-chain scaling options, such as developing a Mimblewimble side-chain, exploring the possibility of Lightning Network so atomic swaps can be performed, and Tumblebit.
In a post on the Monero subreddit from roughly a month ago, monero moderator u/dEBRUYNE_1 supports Spagni's statements. dEBRUYNE_1 clarifies the issue of scalability:
"In Bitcoin, the main chain is constrained and fees are ludicrous. This results in users being pushed to second layer stuff (e.g. sidechains, lightning network). Users do not have optionality in Bitcoin. In Monero, the goal is to make the main-chain accessible to everyone by keeping fees reasonable. We want users to have optionality, i.e., let them choose whether they'd like to use the main chain or second layer stuff. We don't want to take that optionality away from them."
When the Spagni CNBC video was recently linked to the Monero subreddit, it was met with lengthy debate and discussion from both users and developers. u/ferretinjapan summarised the issue explaining:
"Monero has all the mechanisms it needs to find the balance between transaction load, and offsetting the costs of miner infrastructure/profits, while making sure the network is useful for users. But like the interviewer said, the question is directed at "right now", and Fluffys right to a certain extent, Monero's transactions are huge, and compromises in blockchain security will help facilitate less burdensome transactional activity in the future. But to compare Monero to Bitcoin's transaction sizes is somewhat silly as Bitcoin is nowhere near as useful as monero, and utility will facilitate infrastructure building that may eventually utterly dwarf Bitcoin. And to equate scaling based on a node being run on a desktop being the only option for what classifies as "scalable" is also an incredibly narrow interpretation of the network being able to scale, or not. Given the extremely narrow definition of scaling people love to (incorrectly) use, I consider that a pretty crap question to put to Fluffy in the first place, but... ¯_(ツ)_/¯"
u/xmrusher also contributed to the discussion, comparing Bitcoin to Monero using this analogous description:
"While John is much heavier than Henry, he's still able to run faster, because, unlike Henry, he didn't chop off his own legs just so the local wheelchair manufacturer can make money. While Morono has much larger transactions then Bitcoin, it still scales better, because, unlike Bitcoin, it hasn't limited itself to a cripplingly tiny blocksize just to allow Blockstream to make money."
Setting up a wallet can still be time consuming
It's time consuming and can be somewhat difficult for new cryptocurrency users to set up their own wallet using the GUI wallet or the Command Line Wallet. In order to strengthen and further decentralize the Monero network, users are encouraged to run a full node for their wallet, however this can be an issue because it can take up to 24-48 hours for some users depending on their hard-drive and internet speeds. To mitigate this issue, users can run a remote node, meaning they can remotely connect their wallet to another node in order to perform transactions, and in the meantime continue to sync the daemon so in the future they can then use their own node.
For users that do run into wallet setup issues, or any other problems for that matter, there is an extremely helpful troubleshooting thread on the Monero subreddit which can be found here. And not only that, unlike some other cryptocurrency subreddits, if you ask a question, there is always a friendly community member who will happily assist you. is a fantastic resource too!
Despite still being difficult to use, the user-base and price may increase dramatically once it is easier to use. In addition, others believe that when hardware wallets are available more users will shift to Monero.


I actually still feel a little shameful for promoting Monero here, but feel a sense of duty to do so.
Monero is transitioning into an unstoppable altruistic beast. This year offers the implementation of many great developments, accompanied by the likelihood of a dramatic increase in price.
I request you discuss this post, point out any errors I have made, or any information I may have neglected to include. Also, if you believe in the Monero project, I encourage you to join your local Facebook or Reddit cryptocurrency group and spread the word of Monero. You could even link this post there to bring awareness to new cryptocurrency users and investors.
I will leave you with an old on-going joke within the Monero community - Don't buy Monero - unless you have a use case for it of course :-) Just think to yourself though - Do I have a use case for Monero in our unpredictable Huxleyan society? Hint: The answer is ?
Edit: Added in the Tail Emission section, and noted Dan Bilzerian as a Monero investor. Also added information regarding the XMR.TO payment service. Added info about hardfork
submitted by johnfoss69 to CryptoCurrency [link] [comments]

Bitcoin Lightning Network è in testnet, vediamo come funziona Create A Wallet (Testnet V0.2) Open Source Live and Testnet Block Explorer for Bitcoin, Ethereum, Litecoin, Neo, Stellar Ravencoin Asset Creation on Testnet [Video tutorial] Installation of a testnet node by hawky

The Explorer provides block, transaction, and address data for the Bitcoin Cash (BCH) and Bitcoin (BTC) chains. The data is displayed within an awesome interface and is available in several different languages. The testnet is an alternative Bitcoin block chain, to be used for testing. Testnet coins are separate and distinct from actual bitcoins, and are never supposed to have any value. This allows application developers or bitcoin testers to experiment, without having to use real bitcoins or worrying about breaking the main bitcoin chain. Run bitcoin-qt or bitcoind with the -testnet flag to use the ... The Explorer provides block, transaction, and address data for the Bitcoin Cash (BCH) and Bitcoin (BTC) chains. The data is displayed within an awesome interface and is available in several different languages. Buying crypto like Bitcoin and Ether is as easy as verifying your identity, adding a payment and clicking "Buy". Sign up for our Wallet today. Yes, in bitcoin an address begins with "1" or "3", in testnet bitcoin an address begins with "m" or "2". In the case of Ethereum both addresses can be used, but you can't transfer ether from Rinkeby to the real network. The same for Eos, you can have a testnet account only in testnet and not in mainnet and viceversa.

[index] [1572] [46031] [4724] [23898] [34876] [17528] [39142] [20890] [23588] [27660]

Bitcoin Lightning Network è in testnet, vediamo come funziona

L'implementazione Lighning Network su Bitcoin è disponibile sulla rete pubblica testnet, ora si possono avere transazioni economiche e veloci e pagarci il caffé! Vediamo come funziona ... RSK is the first open source smart contract platform with 2-way reference to Bitcoin, which also awards the Bitcoin miners via the merger of production which... Open Source Live and Testnet Block Explorer GitHub Repository: Working on a blockchain pr... Ravencoin Testnet Faucet and Block Explorer Nothing on this channel is financial advice. My Mining Rig Parts Motherboard: Processor ... Download this app to test your devices internet speed. You will need a mouse or pointing device to use this on most devices but it works very well. Download ...