SmartCash - The Business Focused & Community Driven Cryptocurrency
SmartCash is an easy to use, fast, and secure cryptocurrency that can support everyday use such as business payments and daily transactions. SmartCash has a unique decentralized governance system and innovative technologies such as SmartCard and the Point of Sale App. SmartCash is pushing the limits of blockchain technology with tools that support entrepreneurship and innovation.
New England New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/ NewEnglandcoin Symbol: NENG NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones. Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt. 1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377 NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number Bitcoin Fork - Suitable for Home Hobbyists NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs. The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity. MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018) https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software. Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%. NENG v1.4.0 release enabled CPU mining inside android phones. Youtube Video Tutorial How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG. We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange. Twitter Airdrop Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners Graphic Redesign Bounty Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form. Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues. Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1 Milestones
Sep 3, 2018 - Genesis block was mined, NewEnglandcoin created
Sep 8, 2018 - github source uploaded, Window wallet development work started
Sep 11,2018 - Window Qt Graphic wallet completed
Sep 12,2018 - NewEnglandcoin Launched in both Bitcointalk forum and Marinecoin forum
Sep 14,2018 - NewEnglandcoin is listed at ShorelineCrypto Exchange
Sep 17,2018 - Block Explorer is up
Nov 23,2018 - New Source/Wallet Release v1.1.1 - Enabled Dynamic Addjustment on Mining Hashing Difficulty
Nov 28,2018 - NewEnglandcoin became CPU minable coin
Nov 30,2018 - First Retail Real Life usage for NewEnglandcoin Announced
Dec 28,2018 - Cheetah_Cpuminer under Linux is released
Dec 31,2018 - NENG Technical Whitepaper is released
Jan 2,2019 - Cheetah_Cpuminer under Windows is released
Jan 12,2019 - NENG v1.1.2 is released to support MacOS GUI CLI Wallet
Jan 13,2019 - Cheetah_CpuMiner under Mac is released
Feb 11,2019 - NewEnglandcoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Mar 16,2019 - NewEnglandcoin v126.96.36.199 Released - Ubuntu 18.04 Wallet Binary Files
Apr 7, 2019 - NENG Report on Security, Decentralization, Valuation
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Sep 1, 2019 - Shoreline Tradingbot project is Launched by ShorelineCrypto
Dec 19, 2019 - Shoreline Tradingbot v1.0 is Released by ShorelineCrypto
Jan 30, 2020 - Scrypt RandomSpike - NENG v1.3.0 Hardfork Proposed
Feb 24, 2020 - Scrypt RandomSpike - NENG core v1.3.0 Released
Jun 19, 2020 - Linux scripts for Futurebit Moonlander2 USB ASIC on solo mining Released
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining and Ubuntu 20.04 support
Jul 21, 2020 - NENG v188.8.131.52 Released for MacOS Wallet Upgrade with Catalina
Jul 30, 2020 - NENG v184.108.40.206 Released for Linux Wallet Upgrade with 8 Distros
Aug 11, 2020 - NENG v220.127.116.11 Released for Android arm64 Upgrade, Chromebook Support
Aug 30, 2020 - NENG v18.104.22.168 Released for Android/Chromebook with armhf, better hardware support
2018 Q3 - Birth of NewEnglandcoin, window/linux wallet - Done
2018 Q4 - Decentralization Phase I
Blockchain Upgrade - Dynamic hashing algorithm I - Done
Cheetah Version I- CPU Mining Automation Tool on Linux - Done
2019 Q1 - Decentralization Phase II
Cheetah Version II- CPU Mining Automation Tool on Window/Linux - Done
Blockchain Upgrade Dynamic hashing algorithm II - Done
2019 Q2 - Fiat Phase I
Assessment of Risk of 51% Attack on NENG - done
Launch of Fiat USD/NENG offering for U.S. residents - done
Initiation of Mobile Miner Project - Done
2019 Q3 - Shoreline Tradingbot, Mobile Project
Evaluation and planning of Mobile Miner Project - on Hold
Initiation of Trading Bot Project - Done
2019 Q4 - Shoreline Tradingbot
Shoreline tradingbot Release v1.0 - Done
2020 Q1 - Evaluate NENG core, Mobile Wallet Phase I
NENG core Decentralization Security Evaluation for v1.3.x - Done
Light Mobile Wallet Project Initiation, Evaluation
2020 Q2 - NENG Core, Mobile Wallet Phase II
NENG core Decentralization Security Hardfork on v1.3.x - Scrypt RandomSpike
Light Mobile Wallet Project Design, Coding
2020 Q3 - NENG core, NENG Mobile Wallet Phase II
Review on results of v1.3.x, NENG core Dev Decision on v1.4.x, Hardfork If needed
Light Mobile Wallet Project testing, alpha Release
2020 Q4 - Mobile Wallet Phase III
Light Mobile Wallet Project Beta Release
Light Mobile Wallet Server Deployment Evaluation and Decision
Reddcoin (#RDD) May 2020 Team Update, or “New Wallets & What to Expect when You’re Expecting PoSV v2”
Link to Medium post -> https://medium.com/@techadept/reddcoin-rdd-may-2020-team-update-or-what-to-expect-when-youre-expecting-posv-v2-b708319221ce?sk=b5eafc57b67327d99a35380f390d77ca Hey, ReddHeads! To new ReddHeads, welcome! To old ReddHeads, welcome back! It’s an exciting time in Reddcoin (RDD) for a lot of reasons, and we, the Reddcoin Core development team, wanted to get a brief update out to touch base on some of the highlights. Attached are some screenshots of our work to enhance security and interoperability, and to extend support to MacOS Catalina in our newest v3.10.1 wallet. This wallet release also includes components and performance & security upgrades taken from the Bitcoin 0.10 codebase, and we will be following much of that same development and enhancement in our Reddcoin Core wallet in the future, with 0.11 up next. This release is not a required upgrade (except for Catalina users), but will benefit user experience and security significantly. We’ll be publishing, of course, a full public changelog, hashes and commit list in Github along with open source code and compiled executables upon release. But the major changes in Reddcoin v3 are just about to start, as PoSV v2 gets ready to activate. Released to the community on 12/24/19, the blockchain has (at time of writing) reached 8197 of the required 9000 block threshold, or 91.08% of our goal of supermajority. If you haven’t upgraded yet, or aren’t staking, it’s time. After PoSV v2 activation, older (v2.x, v1.x) wallets will not be able to send transactions or stake. We anticipate activation to be reached within a very short time period, especially once our Mac ReddHeads are able to participate, and as such we want to ensure that information for the general community is available and up to date. 1) AM I GOING TO LOSE MY REDDCOIN (RDD)?? a. NO. This is a soft-fork, and whether you’ve upgraded to a v3 wallet or not, you cannot lose your coins. The blockchain itself will remain the same, it is only the rules of staking that are changing. Older wallets WILL stop functioning immediately after the threshold is passed and PoSV v2 activates, but all that is required at that point to restore functionality is to install the new v3 wallet. If you need help, please join our Telegram or Discord live chats for community or Dev help directly. No ReddHead left behind! 2) WHAT DO I NEED TO DO?? a. If you’re staking, make sure you’re using a v3 wallet, preferably the latest version. Right now, that is v3.0.1, in a few days with the above noted release it will be v3.10.1. You may also wish to use the “Backup…” function at this time to make sure you have a backup of the only important file you need, the “wallet.dat” file. There are no mobile staking options at this time due to the nature of our PoSV protocol, but you can deposit coins in the dev team-run ReddBot on Telegram to stake if you have no other options until a mobile staking option is made available. b. If you’re not staking, or are holding on Coinomi, or Guarda, or other 3rd party wallets, or on an exchange, or a paper wallet, you will also have no operational issues, but of course you’re encouraged to help secure the network and validate transactions, by starting to stake. 3) I’M BORED. ENTERTAIN ME! a. OK. As successful as our first meetup was, we agree. Look for an upcoming benefit concert from Reddcoin and hopscotchmafiamusic.com at the end of this month. No, really. Free awesome music, cool people, come have a bit of fun with the ReddHead community virtually! 4) I’M HUNGRY. FEED ME! a. Well…with the activation of PoSV v2, and the creation of Reddcoin’s self- funded development mechanism, we’re very excited to be able to provide at least some resources and RDD toward the Reddcoin Community Food & Supply Bank initiative in the near future. Reddcoin Core will also be donating any funds received in connection with the above concert event to worthy and working charities, especially if we can convince them to receive RDD (or BTC). Watch for further info about this and other charity initiatives to come. Our own efforts rely on PoSV v2 activation, but will be documented publicly and transparently as they evolve. 5) I WAS USING RDD AND THEN X (or Y or Z) HAPPENED AND NOW I’M BROKE AND SAD AND ANGRY. HELP ME! a. Perhaps you’ve not heard about Reddcoin’s uniquely conceived “Reddcoin Restitution Fund”. Been hacked? Lost a few coins when your computer crashed or your brother formatted your hard drive? Reddcoin has committed a percentage of PoSV v2 funding to give back to users legitimately affected by events beyond their control. Cases of extreme stupidity will be vetted on a case by case basis, obviously fraudulent claims will be laughed at, and all cases will be dependent on a reasonable standard of proof and verification. This is also going to be an evolving and good faith approach to giving back to our real ReddHead community, and will require both transparency and abuse-prevention to be successful, but we look forward to being able to help those who deserve and need it. NOTE: Trading and speculative losses aren’t covered in any of this. Obviously. 6) I WANT TO KNOW MORE! We’re working right now to rebuild our main website www.reddcoin.com into a more informative and resource-rich site, but it’s a good starting point. We are in the process of updating our roadmap to cover the end of 2020 and the future as well, and both of those should be available and will be announced within the next month. a. www.medium.com/@techadept b. www.reddcoin.com/reddpaper and https://reddcoin.com/reddpaper-faq/ c. www.twitter.com/@reddcoin d. www.reddit.com/reddcoin e. https://t.me/ReddcoinOfficial (Telegram chat) g. https://www.facebook.com/reddcoin 7) IS TECHADEPT DRINKING WHILE WRITING THIS UPDATE?? a. Yes. Macallan. Fight me.
It was another month in 2020, like previous months in 2020. Stuck inside, hacking away. We don’t see a consistent blockchain Rust theme to highlight this month, but interesting new Rust crypto and blockchain projects continue to be launched. They are noted in the “Interesting Things” section. Oasis launched what will probably become their mainnet. Congrats to them! Ethereum 2 keeps creeping closer, and it looks like Lighthouse, in Rust, might be the fastest implementation. The Holochain team asked that we highlight the Holochain DevCamp, running until August 27th. Now is your opportunity to learn more about the project. There are a number of other online blockchain hackathons going on this summer, noted in our “Events” section. Could be a good way to spend time this summer instead of going to the beach. Well, anyway, keep on hacking.
This edition of RiB was produced with contributions from Darosior, James Waugh, Ken Shamir, Paulii Good, Taylor Lee, Brian Anderson, and Aimee Zhu. Thank you for your help! RiB needs help to keep up with Rust blockchain projects. If you follow a particular project, or otherwise find information that is beneficial to the Rust & blockchain community, please contribute to the next issue. Either submit a PR to the #14 draft, or Tweet @rust_blockchain.
Each month we like to shine a light on a notable Rust blockchain project. This month that project is… electrs. electrs is a server for the Electrum Bitcoin wallet, written in Rust. Electrum is a light wallet that needs to connect to a server to transact with the Bitcoin network. Although there are public Electrum servers, and they are safe to transact with, they can deanonymize users, so it might be prudent to run one’s own Electrum server, like electrs , or bwt (also written in Rust). As mentioned recently in a blog post, Blockstream, one of the primary Bitcoin developers, uses electrs in its block explorer, esplora, which is live at blockstream.info.
I am super stoked about this. A long time ago (2011-2015), on an old machine (an iMac), I used Armory. I was selling that old machine, so I swept my keys into an electrum wallet, and I replaced the hard drive that was in it knowing one day I would come back to it. Well, a couple years after that, I had issues because I couldn't access the files from that hard drive without another mac (trust me, I tried. I password protected that hard drive so only booting it from a legit mac would grant me access to it). And, I lost my paper backup... Luckily, my friend had an old mac mini he let me borrow, and I sat on it for about another 2 years. Today, I finally pulled my wallet off, and could not remember the password I put on the wallet. Thank god for the btcrecover tool, because that cracked my password in under a second (I remembered what it could of been, but not exactly. I would have not guessed what it actually was). It's not a huge amount of bitcoin. But it was more than I remembered keeping (more than 1). Still face-palming though at some of my transactions. I had my armory wallet going back to 2012. Sooooo many bitcoins went through that wallet, mining on slush with my petty mac GPU. I had one of the first OG ASIC butterfly 60GH/s miners too. If only I had kept more, I could quit my day job now. Oh well. But, I thought I'd share an antitheses to the old "I lost my old wallet. please help!!!" posts. Probably going to continue sitting on it for a few more years. And now that I've regained interest, I'm going to start running a full node again. To the moon!
From time to time, somewhere on social media, the FUD appears about the Cardano project. We can see opinions like “Cardano is just a wallet”, “Cardano never launches main-net”, “PoS will never work”, or “it’s just white-paper”. These are all opinions based on impatience, ignorance of the depth and complexity of the project, or the inability to objectively assess the matter. Often, this FUD is caused intentionally by supporters of a competing project. Just to make competitors more relevant. Let’s look at some facts in today’s article. Cardano is a very complex project Cardano is the first project that is based on formal method development and it is built as a mission-critical project. The IOHK team has done thorough research on all areas related to blockchain and distributed networks. The team studied existing works and sought the best solutions to technical problems in a real environment. The team has published many scientific studies that have undergone a rigorous review and today have countless citations. The team starts production software development only after the specifications are available. The critical parts of the project are written in Haskell. Haskell is a functional programming language that doesn’t allow any side-effects. Blockchain incorporates technological, economic and social components. It is a system that aims to replace the current financial system and compete with the current IT giants. Such a project cannot be done just by giving you a bunch of programmers to make you a mix of Bitcoin and Ethereum. Without an emphasis on overall quality and details, such a system will never work reliably in the long term. On the other hand, such a project can be delivered in just one year. Do we need it? Cardano took a different and more challenging path. If the team simply delivered another blockchain, it would rank among hundreds of similar projects. It was necessary to put together experts to cryptography, software security, distributed networking, threat modeling, protocol design, game theory, operating systems, designers of programming languages, economy, and of course, software architects and programmers. All these people had to work together to deliver the network that would be great in all respects. These are people who are respected leaders in their field and often at the top of their careers. If one network is to serve the whole world, it must be capable of global scalability. It must never stop and allow all people on the planet to freely engage in network consensus. Including cheaters. Such a network will be massively attacked. Cardano must endure it and continue to function smoothly. It is a more complex task than you might think. And believe me, there are not many people in the world who could fully understand that in all details. It takes a lot of time and effort to build such a project. No existing project is capable of mass adoption and is at the same time demonstrably secure and sustainable in the long term. Cardano will be. Global, open, public, permissionless networks are brand new. There was nothing like that before Bitcoin. The first generation of cryptocurrencies suffers from technological imperfection. Often they are in the experimental phase and are improving in full operation. In the case of Bitcoin, everybody is scared to change the first layer, as there is a legitimate concern that something will fail. The second layer can improve something, but it will always creak. The quality of the project is directly related to the quality of the team and the time spent on research, experimentation, implementation, and testing. These phases can’t be underestimated or omitted. If you do, it will fire back at you later. We can see thousands of projects on CoinMarketCap, but few are worth the attention. In ten years, there will be maybe only three of them. Transparency Cardano is one of the most transparent projects in the crypto. CEO of IOHK, Charles Hoskinson, does AMA and status updates very often. Sometimes several times in one month. During AMA you can ask him literally what you want. Other team members have recently started updating us as well. Cardano, as one of the few projects, has all its scientific works publicly available. Anyone can look into them and critically review the content. The number of works increases regularly. If anyone has doubts about the quality of the project, they can try to find some mistakes in these works. And believe me, it will be hard. This work by itself has already pushed the crypt forward by a great deal. So far, nobody has worked out exactly what the ledger is and how it should work, whether PoW is really safe, how to write smart contracts safely, how to create a sustainable economic model, etc. All other projects can benefit from this work. Do not believe that? Well, we can give you one of the many possible examples. Aggelos Kiayias is the chair in cybersecurity and privacy at the University of Edinburgh. His research interests are in computer security, information security, applied cryptography, and foundations of cryptography with a particular emphasis on blockchain technologies and distributed systems, e-voting and secure multiparty protocols, as well as privacy and identity management. He joined IOHK in 2017 as a chief scientist through a long-term consulting agreement between IOHK and the University of Edinburgh, where he is also the director of the Blockchain Technology Laboratory. Aggelos is one of the brains behind Ouroboros PoS. It is relatively easy to find the works in which he participated and the number of citations. You can just open any scientific paper from IOHK, check the list of authors and find the number of citations. You can also easily verify there is no competitor in the whole crypto. Of course, the important thing is to get the scientific work into the source code. And that happens. You can check out GitHub for all the project repositories. Be careful, many people and aggregation sites for some reason only look at the cardano-sl repository. Look at them all! We understand that if you are not a programmer, it will be difficult to judge the quality of code. You just have to educate yourself here if you really want to know what is going on on GitHub. Activity is compared by the number of commits, which is some modification of the source code. Usually, a new piece is added or something old is deleted. You can easily look at the details of each repository. You can see how many people are actively developing the code, you can see what they are working on, how often they add changes, and more. Let’s have a look at the Ouroboros-network repository. Shelley protocol is written in Haskell. The quality and activity of the project can also be judged well by the number of new and already solved issues. If you are in any doubt about any project, learn how to read GitHub activity. In the case of the Cardano project, be absolutely calm. The activity is one of the highest, if not absolutely highest, in the entire crypto-sphere. If anyone tells you otherwise, please refer to the IOHK library and GitHub. You can even check out the site where all the Cardano GitHub data is altogether. Delays are usual in software development We have already talked about how complex the Cardano project is. Believe me, delays are a common thing when creating software. There are plenty of well-described reasons for that. Every software engineer could confirm that. Let’s dive into it just a bit. An accurate estimate during making a software plan is nearly impossible. You always have a bunch of items and tasks for a bunch of engineers. Tasks often overlap and depend on each other. To make it worse, tasks are mostly abstract and it is often hard to predict all possible obstacles. You can measure the performance of the team to improve time estimates but still, you never know when a plan is going to fail due to unexpected problems. Team members have to work together years to have solid certainty about all estimates. Cardano team is international so coordination might a bit more demanding. When some small and seemingly unnecessary tasks are skipped at the beginning, it can happen that there will be unexpected delays just because they have to be handled later. And sometimes, plan or priorities changes. Many engineers are very optimistic when asked how long some tasks could take. They are often wrong. In reality, tasks are usually more complex than engineers think. Team members change over time. IT gurus are a special kind. They like to change jobs very often. If a team expert leaves the team, it may take longer to find an adequate replacement. This also causes a delay. The IOHK team has a lot of members. Delivering 90% of functionality can be relatively easy compared to the last 10%. The biggest problems can arise at the end of development when all the individual components are tested together. Problems encountered at the end of development must be addressed. This often means changing a lot of things or redesigning something. Testing itself is very demanding as a global network must be simulated or the setup. In addition, the software must run on different versions of operating systems. Let’s have a look at some famous software delays. Mac OS X was developed under the name Rhapsody and it was 1997. Version 1 release arrived after 4 years. Windows Vista was originally planned to ship in 2003. Thre was 3 years delay. If you look for more examples, you will find many. A project like Cardano can’t simply be done in a year or two. If Shelley is launched this year, it will actually be very fast. If you look at examples from the crypto-world, you will see a big delay in the delivery of Ethereum 2.0. Count how long the Lightning Network has been built. And look at how many errors and failures we’ve seen. These failures have often led to large financial losses. If you were looking for reasons, you would find that it is caused by a badly designed or implemented software. Of course, it is in the best interest of the team to deliver Cardano to the market as quickly as possible. But certainly not at the cost of technical imperfections. This is not a race against time. A year or two has almost no role if we can see a really good and functional, secure network capable of mass adoption. Learn patience. Software delivery has its phases. First, everything has to be well thought out and designed. The team must be built. Then research and experiments are carried out. During this, the first source code can be written. Then the testing phase takes place. Only after all this can the network reach the public. Testnet has been launched Testnet has been running since the end of 2019. And it is a great success. The team expected an interest of about 100 pool operators. There are over 1000 registered pools. The network is stable and runs almost without problems. People’s interest in Cardano is huge. Community people are working on useful tools. Just check adapools.org or pooltool.io. Pool operators have no problem communicating with the team. All problems are gradually solved and many of them very quickly. Everyone in the world can run their own node and become a pool operator. Who claims that Cardano is just a wallet, he should try it for himself. Do you like smart contracts? Do you want to write one? Well, you can try it. Cardano will have Plutus and Marlowe. You can try both of them on the online playground. No Lambo, sorry Cardano’s not here to get you a Lambo. Charles promised to deliver the most decentralized network, secure smart contracts, project governance and resolved scalability. All based on scientific research. If such a network can be delivered and people adopt it, only then can we say that the team has succeeded. Will that affect the price of ADA coins? Definitely yes. The team must be fully focused on development. Not for the price. So do not complain about the price. Nobody is going to help you. Only you are responsible. Summary IOHK is one of the best teams in the crypto. There is a lot of work behind this team. Everyone can look at it. Nothing is patented. Everything is open-source. We cannot forget to Emurgo and Cardano Foundation. These entities, too, are completely transparent, and much work can be seen behind them. See for yourself. If someone doesn’t see it and claims that Cardano is just a wallet, he must be blind and deaf. The delays in delivering such complex software as Cardano are quite common. Rather, it would be appropriate to say that the team is moving very fast. Cardano has come so far that neither Microsoft nor IBM will be able to compete. Thanks to Cardano, the whole crypto will move up a lot and be more relevant. If you don’t believe anything we have written, you have many opportunities to check it out. So don’t believe us, verify yourself. You can read the full article with all links and images here:https://medium.com/@Cardanians_io/cardano-is-not-just-a-wallet-2c27eab9fac7
Reddcoin (#RDD) May 2020 Team Update, or “New Wallets & What to Expect when You’re Expecting PoSV v2”
Link to Medium post -> https://medium.com/@techadept/reddcoin-rdd-may-2020-team-update-or-what-to-expect-when-youre-expecting-posv-v2-b708319221ce?sk=b5eafc57b67327d99a35380f390d77ca Hey, ReddHeads and Crypto Fans!! To new ReddHeads, welcome! To old ReddHeads, welcome back! It’s an exciting time in Reddcoin (RDD) for a lot of reasons, and we, the Reddcoin Core development team, wanted to get a brief update out to touch base on some of the highlights. Attached are some screenshots of our work to enhance security and interoperability, and to extend support to MacOS Catalina in our newest v3.10.1 wallet. This wallet release also includes components and performance & security upgrades taken from the Bitcoin 0.10 codebase, and we will be following much of that same development and enhancement in our Reddcoin Core wallet in the future, with 0.11 up next. This release is not a required upgrade (except for Catalina users), but will benefit user experience and security significantly. We’ll be publishing, of course, a full public changelog, hashes and commit list in Github along with open source code and compiled executables upon release. But the major changes in Reddcoin v3 are just about to start, as PoSV v2 gets ready to activate. Released to the community on 12/24/19, the blockchain has (at time of writing) reached 8197 of the required 9000 block threshold, or 91.08% of our goal of supermajority. If you haven’t upgraded yet, or aren’t staking, it’s time. After PoSV v2 activation, older (v2.x, v1.x) wallets will not be able to send transactions or stake. We anticipate activation to be reached within a very short time period, especially once our Mac ReddHeads are able to participate, and as such we want to ensure that information for the general community is available and up to date. 1) AM I GOING TO LOSE MY REDDCOIN (RDD)?? a. NO. This is a soft-fork, and whether you’ve upgraded to a v3 wallet or not, you cannot lose your coins. The blockchain itself will remain the same, it is only the rules of staking that are changing. Older wallets WILL stop functioning immediately after the threshold is passed and PoSV v2 activates, but all that is required at that point to restore functionality is to install the new v3 wallet. If you need help, please join our Telegram or Discord live chats for community or Dev help directly. No ReddHead left behind! 2) WHAT DO I NEED TO DO?? a. If you’re staking, make sure you’re using a v3 wallet, preferably the latest version. Right now, that is v3.0.1, in a few days with the above noted release it will be v3.10.1. You may also wish to use the “Backup…” function at this time to make sure you have a backup of the only important file you need, the “wallet.dat” file. There are no mobile staking options at this time due to the nature of our PoSV protocol, but you can deposit coins in the dev team-run ReddBot on Telegram to stake if you have no other options until a mobile staking option is made available. b. If you’re not staking, or are holding on Coinomi, or Guarda, or other 3rd party wallets, or on an exchange, or a paper wallet, you will also have no operational issues, but of course you’re encouraged to help secure the network and validate transactions, by starting to stake. 3) I’M BORED. ENTERTAIN ME! a. OK. As successful as our first meetup was, we agree. Look for an upcoming benefit concert from Reddcoin and hopscotchmafiamusic.com at the end of this month. No, really. Free awesome music, cool people, come have a bit of fun with the ReddHead community virtually! 4) I’M HUNGRY. FEED ME! a. Well…with the activation of PoSV v2, and the creation of Reddcoin’s self- funded development mechanism, we’re very excited to be able to provide at least some resources and RDD toward the Reddcoin Community Food & Supply Bank initiative in the near future. Reddcoin Core will also be donating any funds received in connection with the above concert event to worthy and working charities, especially if we can convince them to receive RDD (or BTC). Watch for further info about this and other charity initiatives to come. Our own efforts rely on PoSV v2 activation, but will be documented publicly and transparently as they evolve. 5) I WAS USING RDD AND THEN X (or Y or Z) HAPPENED AND NOW I’M BROKE AND SAD AND ANGRY. HELP ME! a. Perhaps you’ve not heard about Reddcoin’s uniquely conceived “Reddcoin Restitution Fund”. Been hacked? Lost a few coins when your computer crashed or your brother formatted your hard drive? Reddcoin has committed a percentage of PoSV v2 funding to give back to users legitimately affected by events beyond their control. Cases of extreme stupidity will be vetted on a case by case basis, obviously fraudulent claims will be laughed at, and all cases will be dependent on a reasonable standard of proof and verification. This is also going to be an evolving and good faith approach to giving back to our real ReddHead community, and will require both transparency and abuse-prevention to be successful, but we look forward to being able to help those who deserve and need it. NOTE: Trading and speculative losses aren’t covered in any of this. Obviously. 6) I WANT TO KNOW MORE! We’re working right now to rebuild our main website www.reddcoin.com into a more informative and resource-rich site, but it’s a good starting point. We are in the process of updating our roadmap to cover the end of 2020 and the future as well, and both of those should be available and will be announced within the next month. a. www.medium.com/@techadept b. www.reddcoin.com/reddpaper and https://reddcoin.com/reddpaper-faq/ c. www.twitter.com/@reddcoin d. www.reddit.com/reddcoin e. https://www.facebook.com/reddcoin 7) IS TECHADEPT DRINKING WHILE WRITING THIS UPDATE?? a. Yes. Macallan. Fight me.
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.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows 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. OSX 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. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
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.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
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.
Simplified payment verification for fast mobile performance
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.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
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).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
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).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
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.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
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.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
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.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
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.
Lastupdated2018-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!
Lightning Network White Paper - The protocol has changed since this original paper, but covers the mid-level mechanics of the Lightning Network with an emphasis on the smart contracts that make it trustless
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?
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?
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?
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 http://dev.lightning.community/resources. 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?
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?
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?
So I made a thing - AceTipper! for Bitcoin Cash. If you love tipping in BCH, this app will print your tip as paper wallet to be gifted, keeps track of them to see who actually claims them, and (best of all) you can reclaim the gift after a period of time if it goes unclaimed.
AceTipper is an application that will help you print out paper-wallets for the purposes of tipping Bitcoin Cash (BCH) to people who may or may not be familiar with Bitcoin. This application looks to solve 2 problems that I saw. 1) The need for the recipient (who may not be familiar with Bitcoin) to have to install a wallet in order to get some BCH can be a barrier. So with this app, you print out the tip as a paper wallet so you can hand them out to anyoneanywhere. 2) Another problem I saw was that many folks (like servers at restaurants) may take the Bitcoin Cash tip, out of politeness, but then never claim them. Therefore, you lose your funds for no benefit to anyone. So with AceTipper you can track who actually claims the tip - and if nobody claims it within a period of time of your choosing, you can simply take those funds back. This app manages your tips, prints paper wallets of various designs (one design so far actually), but also allows you to take back your tip if it hasn't been claimed for a period of time - say a year. If you have any feedback, I would love to hear about it. This app is Windows and MacOS. Download the Windows and MacOS Installer from Github bitcointipping for questions / feedback. Some notes: This runs completely on your machine as a desktop application (ElectronJS). The seeds for your wallet are stored on your machine. You are absolutely encouraged to make backups of your wallet seed. This is an open-source application. Here is a sample of what a printed BCH tip looks like.
With the large number of new readers coming to this sub we need to make information easy to access so those readers can make informed decisions. We all know there is an unusually large amount of Fear, Uncertainty and Doubt (FUD) surrounding EOS. Frankly, when clear evidence is provided it’s not that difficult to see EOS for the extremely valuable project it is. This post hopes to begin to put an end to all the misinformation by doing the following:
Giving a clear and concise answer to the most frequently asked questions in regards to EOS.
Giving a more in-depth answer for those who want to read more.
Allowing readers to make informed decisions by making credible information easy to access.
As EOS climbs the ranks we need to recognise there are going to be a lot of skeptical readers coming over and posting their questions. Sometimes they will be irrational, hostile and often just looking for a reaction. We should make it our responsibility to welcome everyone and refrain from responding emotionally to provocative posts, instead providing factual and rational answers. I will add to this post as and when I can, if you have any ideas or spot any mistakes let me know and I'll get them fixed ASAP. Im planning to add a bit on the team, centralisation and DPOS, governance and EOS VC shortly but please let me hear your suggestions!
1. How do you registeclaim your EOS tokens before June 2018?
Select Metamask, MyEtherWallet, or Ethereum Wallet
Follow the guide.
Remember that the reason you need to register your Ethereum ERC-20 address is to include your EOS tokens in order for the balance of your EOS Tokens to be included in the Snapshot if a Snapshot is created, you must register your Ethereum address with an EOS public key. The EOS snapshot will take place prior to the 1 June 2018. After this point your ERC-20 EOS tokens will be frozen. And you will be issued EOS tokens on the EOS blockchain.
So PLEASE REGISTER your Ethereum address NOW, don't forget about it, or plan on doing it some time in the near future.
There are a lot of submissions about this in /eos, so rather than making a new one please reply to this thread with any questions you may have. Don't forget to join the EOS mailing list: https://eos.io/#subscribe and join the EOS community on your platform(s) of choice: Telegram, Discord and/or Facebook. And remember, if anyone instructs you to transfer ETH to an EOS contract address that doesn't match the address found on https://eos.io you are being scammed.
2. How will the token the ERC-20 EOS tokens be transferred to the native blockchain?
There isn't one! Read the long answer then read it again, registering your Ethereum wallet is mandatory!
Within 23 hours after the end of the final period on June 1, 2018 at 22:59:59 UTC, all EOS Tokens will become fixed (ie. frozen) and will become non-transferrable on the Ethereum blockchain. In order to ensure your tokens are transferred over to the native blockchain you must register your Ethereum address with an EOS public key, if you do not you will lose all your tokens! I am not going to link any tutorials as there are many that can be found by searching Google and YouTube. block.one is helping with the development of snapshot software that can be used to capture the EOS token balance and registered EOS public key of wallets on the Ethereum blockchain. It is then down to the community to create the snapshot. This snapshot can be used when generating a genesis block for a blockchain implementing eos.io software. block.one will not be launching EOS blockchains or operating any of their nodes.
Exchange Support Some exchanges have announced that they will support the token swap. Although using this method will undoubtedly be much simpler than registering the tokens yourself it also comes with its pitfalls.
It is highly likely there are going to be multiple networks running on the eos.io software that use the snapshot. It is highly unlikely that exchanges will support them all.
It is highly likely that exchanges will not support airdrops that use the snapshot.
Exchanges that have announced support for the token swap include:
EOS.IO software is aiming to provide a decentralized operating system which can support thousands of industrial scale DApps by enabling vertical and horizontal scaling.
EOS.IO is software that introduces a blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications. This is achieved through an operating system-like construct upon which applications can be built. The software provides accounts, authentication, databases, asynchronous communication and the scheduling of applications across multiple CPU cores and/or clusters. The resulting technology is a blockchain architecture that has the potential to scale to millions of transactions per second, eliminates user fees and allows for quick and easy deployment of decentralized applications.
CEO Brendan Blumer - Founder of ii5 (1group) and okay.com. He has been in the blockchain industry since 2014 and started selling virtual assets at the age of 15. Brenden can be found on the Forbes Cypto Rich List. Brendan can be found on Twitter.
CTO Dan Larimer - Dan's the visionary industry leader who built BitShares, Graphene and Steemit as well as the increasingly popular Proof of Stake Governance and Decentralised Autonomous Organization Concept. He states his mission in life is “to find free market solutions to secure life, liberty, and property for all.”. Dan can also be found on the Forbes Cypto Rich List. Dan can be found on Twitter and Medium.
Partner Ian Grigg - Financial cryptographer who's been building cryptographic ledger platforms for 2+ decades. Inventor of the Ricardian Contract and Triple-Entry Accounting.
6. Which consensus mechanism does EOS use and what are Block Producers?
Delegated Proof of Stake (DPOS) with Byzantine Fault Tolerance. Block Producers (BPs) produce the blocks of the blockchain and are elected by token holders that vote for them. BPs will earn block rewards for their service, these block rewards come in the form of EOS tokens produced by token inflation.
“EOS.IO software utilizes the only known decentralized consensus algorithm proven capable of meeting the performance requirements of applications on the blockchain, Delegated Proof of Stake (DPOS). Under this algorithm, those who hold tokens on a blockchain adopting the EOS.IO software may select block producers through a continuous approval voting system. Anyone may choose to participate in block production and will be given an opportunity to produce blocks, provided they can persuade token holders to vote for them. The EOS.IO software enables blocks to be produced exactly every 0.5 second and exactly one producer is authorized to produce a block at any given point in time. If the block is not produced at the scheduled time, then the block for that time slot is skipped. When one or more blocks are skipped, there is a 0.5 or more second gap in the blockchain. Using the EOS.IO software, blocks are produced in rounds of 126 (6 blocks each, times 21 producers). At the start of each round 21 unique block producers are chosen by preference of votes cast by token holders. The selected producers are scheduled in an order agreed upon by 15 or more producers. Byzantine Fault Tolerance is added to traditional DPOS by allowing all producers to sign all blocks so long as no producer signs two blocks with the same timestamp or the same block height. Once 15 producers have signed a block the block is deemed irreversible. Any byzantine producer would have to generate cryptographic evidence of their treason by signing two blocks with the same timestamp or blockheight. Under this model a irreversible consensus should be reachable within 1 second."
7. How does the voting process work?
The voting process will begin once the Block Producer community releases a joint statement ensuring that it is safe to import private keys and vote. Broadly speaking there will be two methods of voting:
Command Line Interface (CLI) tools
EOS Canada has created eosc, a CLI tool that supports Block Producer voting. Other Block Producer candidates such as LibertyBlock are a releasing web portal that will be ready for main net launch. There will be many more options over the coming weeks, please make sure you are always using a service from a trusted entity. Remember: Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so. Ignoring this warning could result in tokens lost.
8. What makes EOS a good investment?
Team - EOS is spearheaded by the visionary that brought us the hugely successful Bitshares and Steem - arguably with two projects already under his belt there is no one more accomplished in the space.
Funding - EOS is one of the best funded projects in the space. The block.one team has committed $1B to investing in funds that grow the EOS echo system. EOS VC funds are managed by venture leaders distributed around the world to insure founders in all markets have the ability to work directly with local investors. Incentives such as the EOS hackathon are also in place with $1,500,000 USD in Prizes Across 4 Events.
Community Focus - The team is aware that the a projects success depends almost entirely on its adoption. For this reason there has been a huge push to develop a strong world wide community. There is already a surplus number of block producers that have registered their interest and started to ready themselves for the launch and incentives the EOS hackathon are being used to grow the community. A index of projects using EOS can be found at https://eosindex.io/posts.
Technical Advantages - See point 9!
9. What are the unique selling points of EOS?
Potential to scale to millions of transactions per second
This depends entirely on your definition of working product. If a fully featured developer release meets your definition then yes!. Otherwise the public release will be June 2018.
EOS differs from other projects in that it aims to deliver a fully featured version of the software on launch. The Dawn 3.0 RC1 feature complete pre-release became available on April 5th. This version has all the features of the final release that is due June 2018. Further development will involve preparing the final system contract which implements all of the staking, voting, and governance mechanics. The common notion that there is no viewable code published is wrong and the initial Dawn 1.0 release has been available from September 14th 2017.
11. EOS is an ERC-20 token, how can it possibly be a competitor to other platforms?
The ERC-20 token is used only for raising funds during the token distribution; all tokens will be transferred to the native blockchain once launched.
EOS team has clearly stated their reason for choosing the Ethereum network when they described the rationale behind the ICO model. Specifically, the ICO should be a fair and auditable process, with as little trust required as possible. If you believe that an ICO should be fair, auditable, and trustless, you have no choice but to use a decentralized smart contract blockchain to run the ICO, the largest, and by-far most popular of which is Ethereum. Since EOS is intended to be a major competitor for Ethereum, some have seen this as a hypocritical choice. - Stolen from trogdor on Steam (I couldn’t word it any better myself).
12. Why do the eos.io T&C’s say the ERC-20 token has no value?
The EOS T&C’s famously state:
"The EOS Tokens do not have any rights, uses, purpose, attributes, functionalities or features, express or implied, including, without limitation, any uses, purpose, attributes, functionalities or features on the EOS Platform."
This is legal wording to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Most notably Tezos (links below).
This all comes down to legal issues. Anyone who’s been into crypto for 5 minuets knows that government bodies such as the Securities and Exchange Commission (SEC) are now paying attention to crypto in a big way. This legal wording is to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Many token creators that launched ICOs are now in deep water for selling unregistered securities.
A filing from the Tezos lawsuit:
"In sum, Defendants capitalized on the recent enthusiasm for blockchain technology and cryptocurrencies to raise funds through the ICO, illegally sold unqualified and unregistered securities, used a Swiss-based entity in an unsuccessful attempt to evade U.S. securities laws, and are now admittedly engaged in the conversion, selling, and possible dissipation of the proceeds that they collected from the Class through their unregistered offering."
To ensure EOS tokens are not classed as a unregistered security block.one has made it clear that they are creating the EOS software only and won’t launching a public blockchain themselves. This task is left down to the community, or more precisely, the Block Producers (BPs). The following disclaimer is seen after posts from block.one:
"block.one is a software company and is producing the EOS.IO software as free, open source software. This software may enable those who deploy it to launch a blockchain or decentralized applications with the features described above. block.one will not be launching a public blockchain based on the EOS.IO software. It will be the sole responsibility of third parties and the community and those who wish to become block producers to implement the features and/or provide the services described above as they see fit. block.one does not guarantee that anyone will implement such features or provide such services or that the EOS.IO software will be adopted and deployed in any way.”
It is expected that many blockchains using eos.io software will emerge. To ensure DAPPs are created on an ecosystem that aligns with the interests of block.one a $1bn fund will be has been created to incentivise projects to use this blockchain.
“A lot of token distributions only allow a small amount of people to participate. The EOS Token distribution structure was created to provide a sufficient period of time for people to participate if they so choose, as well as give people the opportunity to see the development of the EOS.IO Software prior to making a decision to purchase EOS Tokens.”
It is also worth noting that block.one had no knowledge how much the the token distribution would raise as it is determined by the free market and the length of the token distribution is coded into the Ethereum smart contract, which cannot be changed.
14. Where is the money going from the token distribution?
Funding for the project was raised before EOS was announced, the additional money raised from the token distribution is largely going to fund projects on EOS.
A large portion of the money raised is getting put back into the community to incentivise projects using eos.io software. block.one raised all the money they needed to develop the software before the ERC-20 tokens went on sale. There are some conspiracies that block.one are pumping the price of EOS using the funds raised. The good thing about blockchain is you can trace all the transactions, which show nothing of the sort. Not only this but the EOS team are going to have an independent audit after the funding is complete for piece of mind.
From eos.io FAQ:
“block.one intends to engage an independent third party auditor who will release an independent audit report providing further assurances that block.one has not purchased EOS Tokens during the EOS Token distribution period or traded EOS Tokens (including using proceeds from the EOS Token distribution for these purposes). This report will be made available to the public on the eos.io website.”
A more complete list of EOS projects can be found at eosindex.io.
16. Dan left his previous projects, will he leave EOS?
When EOS has been created Dan will move onto creating projects for EOS with block.one.
When a blockchain project has gained momentum and a strong community has formed the project takes on a life of its own and the communities often have ideas that differ from the creators. As we have seen with the Bitcoin and Ethereum hark forks you cant pivot a community too much in a different direction, especially if its changing the fundamentals of the blockchain. Instead of acting like a tyrant Dan has let the communities do what they want and gone a different way. Both the Bitshares and Steem were left in a great position and with Dans help turned out to be two of the most successful blockchain projects to date. Some would argue the most successful projects that are actually useable and have a real use case. What Dan does best is build the architecture and show whats possible. Anyone can then go on to do the upgrades. He is creating EOS to build his future projects upon it. He has stated he loves working at block.one with Brendan and the team and there is far too much momentum behind EOS for him to possibly leave.
No one could have better knowledge on this subject than our Block Producer candidates, I have chosen to look to EOS New York for this answer:
"DDoS'ing a block producing is not as simple as knowing their IP address and hitting "go". We have distributed systems engineers in each of our candidate groups that have worked to defend DDoS systems in their careers. Infrastructure can be built in a way to minimize the exposure of the Block Producing node itself and to prevent a DDoS attack. We haven't published our full architecture yet but let's take a look at fellow candidate EOSphere to see what we mean. As for the launch of the network, we are assuming there will be attacks on the network as we launch. It is being built into the network launch plans. I will reach out to our engineers to get a more detailed answer for you. What also must be considered is that there will be 121 total producing and non-producing nodes on the network. To DDoS all 121 which are located all around the world with different security configurations at the exact same time would be a monumental achievement."
18. If block producers can alter code how do we know they will not do so maliciously?
Block producers are voted in by stake holders.
Changes to the protocol, constitution or other updates are proposed to the community by block producers.
Changes takes 2 to 3 months due to the fact block producers must maintain 15/21 approval for a set amount of time while for changes to be processed.
To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation.
For this question we must understand the following.
Governance and why it is used.
The process of upgrading the protocol, constitution & other updates.
Dan’s view on open-entry systems built around anonymous participation.
Governance Cryptography can only be used to prove logical consistency. It cannot be used to make subjective judgment calls, determine right or wrong, or even identify truth or falsehood (outside of consistency). We need humans to perform these tasks and therefore we need governance! Governance is the process by which people in a community:
Reach consensus on subjective matters of collective action that cannot be captured entirely by software algorithms;
Carry out the decisions they reach; and
Alter the governance rules themselves via Constitutional amendments.
Embedded into the EOS.IO software is the election of block producers. Before any change can be made to the blockchain these block producers must approve it. If the block producers refuse to make changes desired by the token holders then they can be voted out. If the block producers make changes without permission of the token holders then all other non-producing full-node validators (exchanges, etc) will reject the change.
Upgrade process The EOS.IO software defines the following process by which the protocol, as defined by the canonical source code and its constitution, can be updated:
Block producers propose a change to the constitution and obtains 15/21 approval.
Block producers maintain 15/21 approval of the new constitution for 30 consecutive days.
All users are required to indicate acceptance of the new constitution as a condition of future transactions being processed.
Block producers adopt changes to the source code to reflect the change in the constitution and propose it to the blockchain using the hash of the new constitution.
Block producers maintain 15/21 approval of the new code for 30 consecutive days.
Changes to the code take effect 7 days later, giving all non-producing full nodes 1 week to upgrade after ratification of the source code.
All nodes that do not upgrade to the new code shut down automatically.
By default, configuration of the EOS.IO software, the process of updating the blockchain to add new features takes 2 to 3 months, while updates to fix non-critical bugs that do not require changes to the constitution can take 1 to 2 months.
Open-entry systems built around anonymous participation To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation. Dan's quote:
"The only way to maintain the integrity of a community is for the community to have control over its own composition. This means that open-entry systems built around anonymous participation will have no means expelling bad actors and will eventually succumb to profit-driven corruption. You cannot use stake as a proxy for goodness whether that stake is held in a bond or a shareholder’s vote. Goodness is subjective and it is up to each community to define what values they hold as good and to actively expel people they hold has bad. The community I want to participate in will expel the rent-seeking vote-buyers and reward those who use their elected broadcasting power for the benefit of all community members rather than special interest groups (such as vote-buyers). I have faith that such a community will be far more competitive in a market competition for mindshare than one that elects vote buyers."
19. What is the most secure way to generate EOS key pairs?
Block producer candidates EOS Cafe and EOS New York have come forward to help the community with this topic. The block producer candidate eosnewyork has kindly posted a tutorial on steemit detailing the steps that need to be taken to generate key pairs using the official code on the EOS.IO Github. The block producer candidate eoscafe has gone a step further and released an Offline EOS Key Generator application complete with GUI for Windows, Linux & Mac. Not only can this application generate key pairs but it can also validate key pairs and resolve public keys from private keys. This application has also been vouched for by EOS New York
Click the green "open generate-wallet.html" button in the Firefox window, and then generate and print all the paper wallets you need. Tip: To shut down/reboot, look for a 'gear' icon in the upper-right corner. Try to eject your CD before the computer begins the reboot process. (Mac: hold down the mouse button while rebooting. PC: use the eject ... Let’s find out in this detailed guide on how to create a Bitcoin paper wallet. Introduction. You may have heard the saying “not your keys, not your crypto.” One of the best things about Bitcoin is that it gives you complete control over your funds. As long as you keep your private key safe and secure, no-one else has access to your holdings. Of course, depending on what you wish to do ... A Bitcoin Cash SPV Wallet. Control your own private keys. Easily back up your wallet with a mnemonic seed phrase. Enjoy high security without downloading the blockchain or running a full node. Download Latest Version 4.2.0 Electron Cash now comes with the CashFusion privacy tool. Step 2. Print the Paper Wallet. Click the Paper Wallet tab and print the page on high quality setting. Never save the page as a PDF file to print it later since a file is more likely to be hacked than a piece of paper. Step 3. Fold the Paper Wallet. Fold your new Paper wallet following the lines. You can insert one side inside the other to lock ... In order to do this in the most correct form I’m going to give you the most thorough, reasonably secure version of creating a Bitcoin Paper Wallet. There are some steps you could add to this, but I feel that they are superfluous. However, it is possible to do this Tutorial without doing some of the steps. What you must understand is that, in taking shortcuts, you are possibly introducing ...
[TUTORIAL] Como gastar bitcoins de uma paper wallet.
Bitcoin 101 - Intro to Paper Wallets & Cold Storage - Bitcoin Security & Fun with Sloppy Wallets - Duration: 26:57. CRI Recommended for you. 26:57. Bitcoin 101 - Getting Your BTCs out of Your ... Aprenda como gastar os bitcoins de uma paper wallet. ;) [PARTE 1] Como criar uma paper wallet no modo super seguro. https://youtu.be/5ibH6Eube74 Projeto ... Watch this short videoto show you the problems you have using a paper wallet generator for bitcoin, ethereum, cryptos, What is a paper wallet? What is Bitcoin wallet and how it works? SUBSCRIBE FOR MORE HOW MUCH - http://shorturl.at/arBHL Did you know? You can make Bitcoin Paper Wallets even if you don't own any bitcoins! Here is a list of... I have created this to show you the difference between a paperwallet and the client wallet. I am still trying to find a way to check the balance on the paper...