Wallet won't sync - Why your wallet is not syncing and how
Wallet won't sync - Why your wallet is not syncing and how
How to recover your corrupt or deleted Bitcoin Core wallet
My Wallet says Out Of Sync, how do I get it to sync
How can I recover funds from a Bitcoin Core wallet.dat
0.14.0 Runtime Error/Out of memory · Issue #9969 · bitcoin
Gridcoin 18.104.22.168-Leisure "Elizabeth" Release
The core developers are pleased to present the 22.214.171.124 Elizabeth milestone leisure release. This is a leisure release primarily aimed at non-mandatory items and bug fixes leading up to the Fern mandatory milestone release. This release also enables us to whitelist teams other than Gridcoin as a stepping stone for the implementation of no team requirement in Fern. Enjoy! https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/126.96.36.199 Changelog...
Add freedesktop.org desktop file and icon set #1438 (@a123b)
Your Guide to Monero, and Why It Has Great Potential
/////Your Guide to Monero, and Why It Has Great Potential/////
Marketing. It's a dirty word for most members of the Monero community. It is also one of the most divisive words in the Monero community. Yet, the lack of marketing is one of the most frustrating things for many newcomers. This is what makes this an unusual post from a member of the Monero community. This post is an unabashed and unsolicited analyzation of why I believe Monero to have great potential. Below I have attempted to outline different reasons why Monero has great potential, beginning with upcoming developments and use cases, to broader economic motives, speculation, and key issues for it to overcome. I encourage you to discuss and criticise my musings, commenting below if you feel necessary to do so.
Bulletproofs - A Reduction in Transaction Sizes and Fees Since the introduction of Ring Confidential Transactions (Ring CT), transaction amounts have been hidden in Monero, albeit at the cost of increased transaction fees and sizes. In order to mitigate this issue, Bulletproofs will soon be added to reduce both fees and transaction size by 80% to 90%. This is great news for those transacting smaller USD amounts as people commonly complained Monero's fees were too high! Not any longer though! More information can be found here. Bulletproofs are already working on the Monero testnet, and developers were aiming to introduce them in March 2018, however it could be delayed in order to ensure everything is tried and tested. Multisig Multisig has recently been merged! Mulitsig, also called multisignature, is the requirement for a transaction to have two or more signatures before it can be executed. Multisig transactions and addresses are indistinguishable from normal transactions and addresses in Monero, and provide more security than single-signature transactions. It is believed this will lead to additional marketplaces and exchanges to supporting Monero. Kovri Kovri is an implementation of the Invisible Internet Project (I2P) network. Kovri uses both garlic encryption and garlic routing to create a private, protected overlay-network across the internet. This overlay-network provides users with the ability to effectively hide their geographical location and internet IP address. The good news is Kovri is under heavy development and will be available soon. Unlike other coins' false privacy claims, Kovri is a game changer as it will further elevate Monero as the king of privacy. Mobile Wallets There is already a working Android Wallet called Monerujo available in the Google Play Store. X Wallet is an IOS mobile wallet. One of the X Wallet developers recently announced they are very, very close to being listed in the Apple App Store, however are having some issues with getting it approved. The official Monero IOS and Android wallets, along with the MyMonero IOS and Android wallets, are also almost ready to be released, and can be expected very soon. Hardware Wallets Hardware wallets are currently being developed and nearing completion. Because Monero is based on the CryptoNote protocol, it means it requires unique development in order to allow hardware wallet integration. The Ledger Nano S will be adding Monero support by the end of Q1 2018. There is a recent update here too. Even better, for the first time ever in cryptocurrency history, the Monero community banded together to fund the development of an exclusive Monero Hardware Wallet, and will be available in Q2 2018, costing only about $20! In addition, the CEO of Trezor has offered a 10BTC bounty to whoever can provide the software to allow Monero integration. Someone can be seen to already be working on that here. TAILS Operating System Integration Monero is in the progress of being packaged in order for it to be integrated into TAILS and ready to use upon install. TAILS is the operating system popularised by Edward Snowden and is commonly used by those requiring privacy such as journalists wanting to protect themselves and sources, human-right defenders organizing in repressive contexts, citizens facing national emergencies, domestic violence survivors escaping from their abusers, and consequently, darknet market users. In the meantime, for those users who wish to use TAILS with Monero, u/Electric_sheep01 has provided Sheep's Noob guide to Monero GUI in Tails 3.2, which is a step-by-step guide with screenshots explaining how to setup Monero in TAILS, and is very easy to follow. Mandatory Hardforks Unlike other coins, Monero receives a protocol upgrade every 6 months in March and September. Think of it as a Consensus Protocol Update. Monero's hard forks ensure quality development takes place, while preventing political or ideological issues from hindering progress. When a hardfork occurs, you simply download and use the new daemon version, and your existing wallet files and copy of the blockchain remain compatible. This reddit post provides more information. Dynamic fees Many cryptocurrencies have an arbitrary block size limit. Although Monero has a limit, it is adaptive based on the past 100 blocks. Similarly, fees change based on transaction volume. As more transactions are processed on the Monero network, the block size limit slowly increases and the fees slowly decrease. The opposite effect also holds true. This means that the more transactions that take place, the cheaper the fees! Tail Emission and Inflation There will be around 18.4 million Monero mined at the end of May 2022. However, tail emission will kick in after that which is 0.6 XMR, so it has no fixed limit. Gundamlancer explains that Monero's "main emission curve will issue about 18.4 million coins to be mined in approximately 8 years. (more precisely 18.132 Million coins by ca. end of May 2022) After that, a constant "tail emission" of 0.6 XMR per 2-minutes block (modified from initially equivalent 0.3 XMR per 1-minute block) will create a sub-1% perpetual inflatio starting with 0.87% yearly inflation around May 2022) to prevent the lack of incentives for miners once a currency is not mineable anymore. Monero Research Lab Monero has a group of anonymous/pseudo-anonymous university academics actively researching, developing, and publishing academic papers in order to improve Monero. See here and here. The Monero Research Lab are acquainted with other members of cryptocurrency academic community to ensure when new research or technology is uncovered, it can be reviewed and decided upon whether it would be beneficial to Monero. This ensures Monero will always remain a leading cryptocurrency. A recent end of 2017 update from a MRL researcher can be found here.
///Monero's Technology - Rising Above The Rest///
Monero Has Already Proven Itself To Be Private, Secure, Untraceable, and Trustless Monero is the only private, untraceable, trustless, secure and fungible cryptocurrency. Bitcoin and other cryptocurrencies are TRACEABLE through the use of blockchain analytics, and has lead to the prosecution of numerous individuals, such as the alleged Alphabay administrator Alexandre Cazes. In the Forfeiture Complaint which detailed the asset seizure of Alexandre Cazes, the anonymity capabilities of Monero were self-demonstrated by the following statement of the officials after the AlphaBay shutdown: "In total, from CAZES' wallets and computer agents took control of approximately $8,800,000 in Bitcoin, Ethereum, Monero and Zcash, broken down as follows: 1,605.0503851 Bitcoin, 8,309.271639 Ethereum, 3,691.98 Zcash, and an unknown amount of Monero". Privacy CANNOT BE OPTIONAL and must be at a PROTOCOL LEVEL. With Monero, privacy is mandatory, so that everyone gets the benefits of privacy without any transactions standing out as suspicious. This is the reason Darknet Market places are moving to Monero, and will never use Verge, Zcash, Dash, Pivx, Sumo, Spectre, Hush or any other coins that lack good privacy. Peter Todd (who was involved in the Zcash trusted setup ceremony) recently reiterated his concerns of optional privacy after Jeffrey Quesnelle published his recent paper stating 31.5% of Zcash transactions may be traceable, and that only ~1% of the transactions are pure privacy transactions (i.e., z -> z transactions). When the attempted private transactions stand out like a sore thumb there is no privacy, hence why privacy cannot be optional. In addition, in order for a cryptocurrency to truly be private, it must not be controlled by a centralised body, such as a company or organisation, because it opens it up to government control and restrictions. This is no joke, but Zcash is supported by DARPA and the Israeli government!. Monero provides a stark contrast compared to other supposed privacy coins, in that Monero does not have a rich list! With all other coins, you can view wallet balances on the blockexplorers. You can view Monero's non-existent rich list here to see for yourself. I will reiterate here that Monero is TRUSTLESS. You don't need to rely on anyone else to protect your privacy, or worry about others colluding to learn more about you. No one can censor your transaction or decide to intervene. Monero is immutable, unlike Zcash, in which the lead developer Zooko publicly tweeted the possibility of providing a backdoor for authorities to trace transactions. To Zcash's demise, Zooko famously tweeted:
" And by the way, I think we can successfully make Zcash too traceable for criminals like WannaCry, but still completely private & fungible. …"
Ethereum's track record of immutability is also poor. Ethereum was supposed to be an immutable blockchain ledger, however after the DAO hack this proved to not be the case. A 2016 article on Saintly Law summarised the problematic nature of Ethereum's leadership and blockchain intervention:
" Many ethereum and blockchain advocates believe that the intervention was the wrong move to make in this situation. Smart contracts are meant to be self-executing, immutable and free from disturbance by organisations and intermediaries. Yet the building block of all smart contracts, the code, is inherently imperfect. This means that the technology is vulnerable to the same malicious hackers that are targeting businesses and governments. It is also clear that the large scale intervention after the DAO hack could not and would not likely be taken in smaller transactions, as they greatly undermine the viability of the cryptocurrency and the technology."
Monero provides Fungibility and Privacy in a Cashless World As outlined on GetMonero.org, fungibility is the property of a currency whereby two units can be substituted in place of one another. Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR. Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation coinbase transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the blockchain in perpetuity. A great example of Bitcoin's lack of fungibility was reposted by u/ViolentlyPeaceful:
"Imagine you sell cupcakes and receive Bitcoin as payment. It turns out that someone who owned that Bitcoin before you was involved in criminal activity. Now you are worried that you have become a suspect in a criminal case, because the movement of funds to you is a matter of public record. You are also worried that certain Bitcoins that you thought you owned will be considered ‘tainted’ and that others will refuse to accept them as payment."
This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies. Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain. The world is moving cashless. Fact. The ramifications of this are enormous as we move into a cashless world in which transactions will be tracked and there is a potential for data to be used by third parties for adverse purposes. While most new cryptocurrency investors speculate upon vaporware ICO tokens in the hope of generating wealth, Monero provides salvation for those in which financial privacy is paramount. Too often people equate Monero's features with criminal endeavors. Privacy is not a crime, and is necessary for good money. Transparency in Monero is possible OFF-CHAIN, which offers greater transparency and flexibility. For example, a Monero user may share their Private View Key with their accountant for tax purposes. Monero aims to be adopted by more than just those with nefarious use cases. For example, if you lived in an oppressive religious regime and wanted to buy a certain item, using Monero would allow you to exchange value privately and across borders if needed. Another example is that if everybody can see how much cryptocurrency you have in your wallet, then a certain service might decide to charge you more, and bad actors could even use knowledge of your wallet balance to target you for extortion purposes. For example, a Russian cryptocurrency blogger was recently beaten and robbed of $425k. This is why FUNGIBILITY IS ESSENTIAL. To summarise this in a nutshell:
"A lack of fungibility means that when sending or receiving funds, if the other person personally knows you during a transaction, or can get any sort of information on you, or if you provide a residential address for shipping etc. – you could quite potentially have them use this against you for personal gain"
Major Investors And Crypto Figureheads Are Interested Ari Paul is the co-founder and CIO of BlockTower Capital. He was previously a portfolio manager for the University of Chicago's $8 billion endowment, and a derivatives market maker and proprietary trader for Susquehanna International Group. Paul was interviewed on CNBC on the 26th of December and when asked what was his favourite coin was, he stated "One that has real fundamental value besides from Bitcoin is Monero" and said it has "very strong engineering". In addition, when he was asked if that was the one used by criminals, he replied "Everything is used by criminals including the US dollar and the Euro". Paul later supported these claims on Twitter, recommending only Bitcoin and Monero as long-term investments. There are reports that "Roger Ver, earlier known as 'Bitcoin Jesus' for his evangelical support of the Bitcoin during its early years, said his investment in Monero is 'substantial' and his biggest in any virtual currency since Bitcoin. Charlie Lee, the creator of Litecoin, has publicly stated his appreciation of Monero. In a September 2017 tweet directed to Edward Snowden explaining why Monero is superior to Zcash, Charlie Lee tweeted:
All private transactions, More tested privacy tech, No tax on miners to pay investors, No high inflation... better investment.
John McAfee, arguably cryptocurrency's most controversial character at the moment, has publicly supported Monero numerous times over the last twelve months(before he started shilling ICOs), and has even claimed it will overtake Bitcoin. Playboy instagram celebrity Dan Bilzerian is a Monero investor, with 15% of his portfolio made up of Monero. Finally, while he may not be considered a major investor or figurehead, Erik Finman, a young early Bitcoin investor and multimillionaire, recently appeared in a CNBC Crypto video interview, explaining why he isn't entirely sold on Bitcoin anymore, and expresses his interest in Monero, stating:
"Monero is a really good one. Monero is an incredible currency, it's completely private."
There is a common belief that most of the money in cryptocurrency is still chasing the quick pump and dumps, however as the market matures, more money will flow into legitimate projects such as Monero. Monero's organic growth in price is evidence smart money is aware of Monero and gradually filtering in. The Bitcoin Flaw A relatively unknown blogger named CryptoIzzy posted three poignant pieces regarding Monero and its place in the world. The Bitcoin Flaw: Monero Rising provides an intellectual comparison of Monero to other cryptocurrencies, and Valuing Cryptocurrencies: An Approach outlines methods of valuing different coins. CryptoIzzy's most recent blog published only yesterday titled Monero Valuation - Update and Refocus is a highly recommended read. It touches on why Monero is much more than just a coin for the Darknet Markets, and provides a calculated future price of Monero. CryptoIzzy also published The Power of Money: A Case for Bitcoin, which is an exploration of our monetary system, and the impact decentralised cryptocurrencies such as Bitcoin and Monero will have on the world. In the epilogue the author also provides a positive and detailed future valuation based on empirical evidence. CryptoIzzy predicts Monero to easily progress well into the four figure range. Monero Has a Relatively Small Marketcap Recently we have witnessed many newcomers to cryptocurrency neglecting to take into account coins' marketcap and circulating supply, blindly throwing money at coins under $5 with inflated marketcaps and large circulating supplies, and then believing it's possible for them to reach $100 because someone posted about it on Facebook or Reddit. Compared to other cryptocurrencies, Monero still has a low marketcap, which means there is great potential for the price to multiply. At the time of writing, according to CoinMarketCap, Monero's marketcap is only a little over $5 billion, with a circulating supply of 15.6 million Monero, at a price of $322 per coin. For this reason, I would argue that this is evidence Monero is grossly undervalued. Just a few billion dollars of new money invested in Monero can cause significant price increases. Monero's marketcap only needs to increase to ~$16 billion and the price will triple to over $1000. If Monero's marketcap simply reached ~$35 billion (just over half of Ripple's $55 billion marketcap), Monero's price will increase 600% to over $2000 per coin. Another way of looking at this is Monero's marketcap only requires ~$30 billion of new investor money to see the price per Monero reach $2000, while for Ethereum to reach $2000, Ethereum's marketcap requires a whopping ~$100 billion of new investor money. Technical Analysis There are numerous Monero technical analysts, however none more eerily on point than the crowd-pleasing Ero23. Ero23's charts and analysis can be found on Trading View. Ero23 gained notoriety for his long-term Bitcoin bull chart published in February, which is still in play today. Head over to his Trading View page to see his chart: Monero's dwindling supply. $10k in 2019 scenario, in which Ero23 predicts Monero to reach $10,000 in 2019. There is also this chart which appears to be freakishly accurate and is tracking along perfectly today. Coinbase Rumours Over the past 12 months there have been ongoing rumours that Monero will be one of the next cryptocurrencies to be added to Coinbase. In January 2017, Monero Core team member Riccardo 'Fluffypony' Spagni presented a talk at Coinbase HQ. In addition, in November 2017 GDAX announced the GDAX Digit Asset Framework outlining specific parameters cryptocurrencies must meet in order to be added to the exchange. There is speculation that when Monero has numerous mobile and hardware wallets available, and multisig is working, then it will be added. This would enable public accessibility to Monero to increase dramatically as Coinbase had in excess of 13 million users as of December, and is only going to grow as demand for cryptocurrencies increases. Many users argue that due to KYC/AML regulations, Coinbase will never be able to add Monero, however the Kraken exchange already operates in the US and has XMfiat pairs, so this is unlikely to be the reason Coinbase is yet to implement XMfiat trading. Monero Is Not an ICO Scam It is likely most of the ICOs which newcomers invest in, hoping to get rich quick, won't even be in the Top 100 cryptocurrencies next year. A large portion are most likely to be pumps and dumps, and we have already seen numerous instances of ICO exit scams. Once an ICO raises millions of dollars, the developers or CEO of the company have little incentive to bother rolling out their product or service when they can just cash out and leave. The majority of people who create a company to provide a service or product, do so in order to generate wealth. Unless these developers and CEOs are committed and believed in their product or service, it's likely that the funds raised during the ICO will far exceed any revenue generated from real world use cases. Monero is a Working Currency, Today Monero is a working currency, here today. The majority of so called cryptocurrencies that exist today are not true currencies, and do not aim to be. They are a token of exchange. They are like a share in a start-up company hoping to use blockchain technology to succeed in business. A crypto-assest is a more accurate name for coins such as Ethereum, Neo, Cardano, Vechain, etc. Monero isn't just a vaporware ICO token that promises to provide a blockchain service in the future. It is not a platform for apps. It is not a pump and dump coin. Monero is the only coin with all the necessary properties to be called true money. Monero is private internet money. Some even describe Monero as an online Swiss Bank Account or Bitcoin 2.0, and it is here to continue on from Bitcoin's legacy. Monero is alleviating the public from the grips of banks, and protests the monetary system forced upon us. Monero only achieved this because it is the heart and soul, and blood, sweat, and tears of the contributors to this project. Monero supporters are passionate, and Monero has gotten to where it is today thanks to its contributors and users.
///Key Issues for Monero to Overcome///
Scalability While Bulletproofs are soon to be implemented in order to improve Monero's transaction sizes and fees, scalability is an issue for Monero that is continuously being assessed by Monero's researchers and developers to find the most appropriate solution. Ricardo 'Fluffypony' Spagni recently appeared on CNBC's Crypto Trader, and when asked whether Monero is scalable as it stands today, Spagni stated that presently, Monero's on-chain scaling is horrible and transactions are larger than Bitcoin's (because of Monero's privacy features), so side-chain scaling may be more efficient. Spagni elaborated that the Monero team is, and will always be, looking for solutions to an array of different on-chain and off-chain scaling options, such as developing a Mimblewimble side-chain, exploring the possibility of Lightning Network so atomic swaps can be performed, and Tumblebit. In a post on the Monero subreddit from roughly a month ago, monero moderator u/dEBRUYNE_1 supports Spagni's statements. dEBRUYNE_1 clarifies the issue of scalability:
"In Bitcoin, the main chain is constrained and fees are ludicrous. This results in users being pushed to second layer stuff (e.g. sidechains, lightning network). Users do not have optionality in Bitcoin. In Monero, the goal is to make the main-chain accessible to everyone by keeping fees reasonable. We want users to have optionality, i.e., let them choose whether they'd like to use the main chain or second layer stuff. We don't want to take that optionality away from them."
"Monero has all the mechanisms it needs to find the balance between transaction load, and offsetting the costs of miner infrastructure/profits, while making sure the network is useful for users. But like the interviewer said, the question is directed at "right now", and Fluffys right to a certain extent, Monero's transactions are huge, and compromises in blockchain security will help facilitate less burdensome transactional activity in the future. But to compare Monero to Bitcoin's transaction sizes is somewhat silly as Bitcoin is nowhere near as useful as monero, and utility will facilitate infrastructure building that may eventually utterly dwarf Bitcoin. And to equate scaling based on a node being run on a desktop being the only option for what classifies as "scalable" is also an incredibly narrow interpretation of the network being able to scale, or not. Given the extremely narrow definition of scaling people love to (incorrectly) use, I consider that a pretty crap question to put to Fluffy in the first place, but... ¯_(ツ)_/¯"
u/xmrusher also contributed to the discussion, comparing Bitcoin to Monero using this analogous description:
"While John is much heavier than Henry, he's still able to run faster, because, unlike Henry, he didn't chop off his own legs just so the local wheelchair manufacturer can make money. While Morono has much larger transactions then Bitcoin, it still scales better, because, unlike Bitcoin, it hasn't limited itself to a cripplingly tiny blocksize just to allow Blockstream to make money."
Setting up a wallet can still be time consuming It's time consuming and can be somewhat difficult for new cryptocurrency users to set up their own wallet using the GUI wallet or the Command Line Wallet. In order to strengthen and further decentralize the Monero network, users are encouraged to run a full node for their wallet, however this can be an issue because it can take up to 24-48 hours for some users depending on their hard-drive and internet speeds. To mitigate this issue, users can run a remote node, meaning they can remotely connect their wallet to another node in order to perform transactions, and in the meantime continue to sync the daemon so in the future they can then use their own node. For users that do run into wallet setup issues, or any other problems for that matter, there is an extremely helpful troubleshooting thread on the Monero subreddit which can be found here. And not only that, unlike some other cryptocurrency subreddits, if you ask a question, there is always a friendly community member who will happily assist you. Monero.how is a fantastic resource too! Despite still being difficult to use, the user-base and price may increase dramatically once it is easier to use. In addition, others believe that when hardware wallets are available more users will shift to Monero.
I actually still feel a little shameful for promoting Monero here, but feel a sense of duty to do so. Monero is transitioning into an unstoppable altruistic beast. This year offers the implementation of many great developments, accompanied by the likelihood of a dramatic increase in price. I request you discuss this post, point out any errors I have made, or any information I may have neglected to include. Also, if you believe in the Monero project, I encourage you to join your local Facebook or Reddit cryptocurrency group and spread the word of Monero. You could even link this post there to bring awareness to new cryptocurrency users and investors. I will leave you with an old on-going joke within the Monero community - Don't buy Monero - unless you have a use case for it of course :-) Just think to yourself though - Do I have a use case for Monero in our unpredictable Huxleyan society? Hint: The answer is ? Edit: Added in the Tail Emission section, and noted Dan Bilzerian as a Monero investor. Also added information regarding the XMR.TO payment service. Added info about hardfork
Groestlcoin September 2019 Development Release/Update!
For a more interactive view of changes, click here In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development. Here is what the team has already announced in the last 3 months since the last development update:
Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.
Shows Onion (Tor) nodes
Shows IPv6 nodes
Supports both main net and test net
Node Checker – Check the status of a remote node
Ability to download node data by CSV, JSON or TXT format
Ability to download unique address data by CSV, JSON or TXT format
This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.
Create Raw Unsigned Groestlcoin transactions
Generates a QR code for the transaction
Compatible with most Groestlcoin wallets including but not restricted to Groestlcoin Core and Electrum-GRS
Estimates final signed transaction size
Taking a raw transaction format and shows its Transaction ID, Transaction Inputs and Outputs
AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.
Update to Groestlcoin Core 2.17.2
Switched to native builds via NDK for Groestlcoin Core resulting in a smaller footprint.
Added embedded tor
Added tor pairing support
TOR upgrade bug fixes
Improved blockchain Sync progress using getblockchaininfo verificationprogress
Improved package download progress bar
Added support for external storage access > Android M
Added support for Android Oreo, including new notification mechanism
Bump Fee (RBF) improvements – Implemented a new fee-bump strategy that can add new inputs, so now any transaction can be fee-bumped. The old strategy was to decrease the value of outputs (starting with change). We will now try the new strategy first, and only use the old as a fallback.
Coin Choser improvements
More likely to construct transactions without change (where possible)
Less likely to construct transactions with really small change
Only spend negative effective value coins when beneficial for privacy
Fix long-standing bug that broke wallets with >65k addresses
Windows binaries: Now build the PyInstaller bootloader ourselves, as this seems to reduce anti-virus false positives
Fix performance regression for large wallets
Fix high-DPI issues related to text fields
Trezor – Allow bypassing 'too old firmware' error
Trezor – Use only the Bridge to scan devices if it is available
Hardware wallets – On Win10-1903, some hardware devices with U2F functionality can only be detected with Administrator privileges. A workaround is to run as Admin, or for Trezor to install the Bridge.
The AppImage Linux x86_64 binary and the Windows setup.exe are now built reproducibly.
Fix watch-only wallets that could not bump fee in some scenarios
Faster transaction signing for segwit inputs or really large transactions.
Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms. Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.
iOS 0.7.3 Changes
Fix BIP70 payments
Updated QR Scanner
Lowered spending limit
Updated DNS Seeds
Fixed URL Scheme
Fixed GRS Name in mailing
Fixed crash upon starting in some scenarios
Android v89 Changes
Use default fee
Republished on Google Play by removing send_sms permissions
[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind
[SOLVED] Thanks for everyone that have helped!
Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this. I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings. I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem. So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0 # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works). And here is when I netstat: sudo netstat -nap|grep bitcoin|grep LISTEN
dcrd: Several steps towards multipeer downloads completed: an optimization to use in-memory block index and a new 1337 chain view. Maintenance: improved test coverage, upgrading dependency management system and preparing for the upcoming Go 1.11 release. dcrwallet: A big change introducing optional privacy-preserving SPV sync mode was merged. In this mode dcrwallet does not download the full blockchain but only gets the "filters", uses them to determine which blocks it needs and fetches them from random nodes on the network. This has on-disk footprint of 300-400 MB and sync time of minutes, compared to ~3.4 GB and sync time of hours for full sync (these are rough estimates).
jy-p: the server side of SPV (in dcrd) was deployed in v1.2.0, the client side of SPV (in dcrwallet) is in our next release, v1.3.0. Still some minor bugs in SPV that are being worked out. There will be an update to add the latest features from BIP 157/158 in the next few months. SPV will be optional in v1.3.0, but it will become the default after we get a proper header commitment for it (#general)
Decrediton: besides regular bugfixes and design improvements, several components are being developed in parallel like SPV mode, Politeia integration and Trezor support. Politeia: testing started on mainnet, thanks to everyone who is participating. A lot of testing, bugfixing and polishing is happening in preparation for full mainnet launch. There are also a few missing features to be added before launch, e.g. capacity to edit a proposal and versioning for that, discussion to remain open once voting starts. Decrediton integration is moving forward, check out this video for a demo and this meta issue for the full checklist. Trezor: Decrediton integration of initial Trezor support is in progress and there is a demo. Android: app design version 2.0 completed. dcrdata: development of several chart visualizations was completed and is awaiting deployment. Specifically, voting agendas and historic charts are merged while ticket pool visualization is in testing. atomicswap: @glendc is seeking reviews of his Ethereum support pull request. Dev activity stats for July: 252 active PRs, 220 master commits, 34,754 added and 12,847 deleted lines spread across 6 repositories. Contributions came from 6-10 developers per repository. (chart)
Hashrate: the month started at 40.5 and ended at 51.6 PH/s, with a low of 33.3 and a new all time high of 68.4 PH/s. F2Pool is leading with 40-45%, followed by the new BeePool at 15-25% and coinmine.pl at 18-23%. Staking: 30-day average ticket price is 92.6 DCR (-2.1). The price started the month at 94.6 and quickly retreated to month's low of 85 until 1,860 tickets were bought within a single period (versus target 720). This pushed the pool of tickets to 41,970 (2.5% above target), which in turn caused 10 price increases in a row to the month's high of 100.4. This was the highest ticket price seen on the new ticket price algorithm which has been in effect since Jul 2017. Second half of the month there was unusually low volatility between 92 and 94 DCR per ticket. Locked DCR held between 3.75 and 3.87 million or 46.6-48.0% of supply (+0.1% from previous peak). Nodes: there are 212 public listening and 216 normal nodes per dcred.eu. Version distribution: 67% on v1.2.0 (+10%), 24% on v1.1.2 (-1%), 7% on v1.1.0 (-7%). Node count data is not perfect but we can see the steady trend of upgrading to v1.2.0. This version of dcrd is notable for serving compact filters. The increased count of such full nodes allows the developers to test SPV client mode in preparations for the upcoming v1.3.0 release.
Obelisk posted three updates in July. For the most recent daily updates join their Discord. New miner from iBeLink: DSM7T hashes Blake256 at 7 TH/s or Blake2b at 3.5 TH/s, consumes 2,100 W and costs $3,800, shipping Aug 5-10. There were also speculations about the mysterious Pangolin Whatsminer DCR with the speed of 44 TH/s at 2,200 W and the cost of $3,888, shipping November. If you know more about it please share with us in #pow-mining channel.
emiliomann: stakebrasil is one of the pools with the lowest number of missed and expired tickets. It was one of the first and has a smaller percentage than the most recent ones who haven’t had the time to do so. (...) The Brazilian pool should be the one with the more servers spread around the world: 6 to decrease the latency. This is to explain to you why the [pool fee] rate of 5% (currently around 0.06 DCR) on the reward is also one of the highest. girino: 8 voting wallets now. I just finished setting up a new one yesterday. All of them in different datacenters, 3 in europe, 3 in north america, 1 in brazil and one in asia. We also have 3 more servers, 1 for the front end, one for "stats" and one for dcrdata. (#general)
On the mining side, Luxor started a new set of pool servers inside mainland China, while zpool has enabled Decred mining. StatX announced Decred integration into their live dashboard and public chat. Decred was added to Satowallet with BTC and ETH trading pairs. Caution: do your best to understand the security model before using any wallet software.
Marina Silva is the first presidential candidate in Brazil using blockchain to keep all their electoral donations transparent and traceable. VotoLegal uses Decred technology, awesome use case! (reddit)
We continue to see institutional interest in DCR. Large block buyers love the concept of staking as a way to earn additional income and appreciate the stakeholder rights it affords them. Likening a DCR investment to an activist shareholdebondholder gives these institutions some comfort while dipping their toes into a burgeoning new asset class.
Targeted advertising reports released for June and July. As usual, reach @timhebel for full versions.
Big news in June: Facebook reversed their policy on banning crypto ads. ICO ads are still banned, but we should be OK. My team filled out the appeal today, so we should hopefully hear something within a few days. (u/timhebel on reddit)
After couple weeks Facebook finally responded to the appeal and the next step is to verify the domain name via DNS. A pack of Stakey Telegram stickers is now available. Have fun!
Meetup in Berlin, Germany hosted by BlueYard Capital. @jz_bz and @lftherios discussed open source incentivization, the value of governance and their respective projects @decredproject and @oscoin. See @issedjur's feedback here. (photos: 1, 2, 3)
O'Reilly Open Source Convention in Portland, USA. @raedah's talk was "Decentralizing decision-making on the blockchain". Read his report here and see on the photos how the Big Stakey was entertaining the public. (photos: 1, 2, 3)
oregonisaac: many open source devs at OSCON were VERY interested in Politeia and it was probably the #1 hook that resulted in lots of long conversations about what makes Decred unique from the ground up. (#politeia)
Blockchain Meetup in Faro, Portugal. Marco Peereboom gave a talk "Decred 101" and answered questions.
Meetup in Lisbon, Portugal on Aug 2. @moo31337 and @mm will be presenting on Decred with talk "Decred 101 - Governance with skin in the game". Co-hosted by The Block Cafe. Free entrance.
Meetup in Taipei, Taiwan on Aug 5. @morphymore will give a short intro on Decred.
OKEx Global Meetup Tour in Ho Chi Minh City, Vietnam on Aug 9. @joshuam will introduce Decred and on-chain governance and take part in a panel discussion.
Twitter: Ari Paul debates "There can be only one" aka "highlander argument". Reddit and Forum: how ticket pool size influences average vote time; roadmap concerns; why ticket price was volatile; ideas for using Reddit chat for dcrtrader and alternative chat systems; insette's write-up on Andrew Stone's GROUP proposal for miner-validated tokenization that is superior to current OP_RETURN-based schemes; James Liu's paper to extend atomic swaps to financial derivatives; what happens when all DCR are mined, tail emission and incentives for miners. Chats: why tickets don't have 100% chance to vote; ideas for more straightforward marketing; long-running chat about world economy and failure modes; @brandon's thoughts on tokenizing everything, ICOs, securities, sidechains and more; challenges of staking with Trezor; ideas how to use CryptoSteel wallet with Decred; why exchange can't stake your coins, how staking can increase security, why the function to export seed from wallet is bad idea and why dcrwallet doesn't ever store the seed; ticket voting math; discussion about how GitHub workflow forces to depend on modern web browser and possible alternatives; funding marketing and education in developing markets, vetting contractors based on deliverables, "Decred contractor clearance", continued in #governance. #dex channel continues to attract thinkers and host chats about influence of exchanges, regulation, HFT, lot sizes, liquidity, on-chain vs off-chain swaps, to name a few topics. #governance also keeps growing and hosting high quality conversations.
In July DCR was trading in USD 56-76 and BTC 0.0072-0.0109 range. A recovery started after a volume boost of up to $10.5 m on Fex around Jul 13, but once Bitcoin headed towards USD ~8,000 DCR declined along with most altcoins. WalletInvestor posted a prediction on dcrtrader. Decred was noticed in top 10 mineable coins on coinmarketcap.com.
One million PCs in China were infected via browser plugins to mine Decred, Siacoin and Digibyte. In a Unchained podcast episode David Vorick shared why ASICs are better than GPUs even if they tend toward mining centralization and also described Obelisk's new Launchpad service. (missed in June issue) Sia project moved to GitLab. The stated reasons are to avoid the risk of depending on centralized service, to avoid vendor lock-in, better continuous integration and testing, better access control and the general direction to support decentralized and open source projects. Luxor explained why PPS pools are better. @nic__carter published slides from his talk "An Overview of Governance in Blockchains" from Zcon0. This article arguing the importance of governance systems dates back to 2007. Bancor wallet was hacked. This reminds us about the fake feeling of decentralizaion, that custody of funds is dangerous and that smart contracts must have minimum complexity and be verifiable. Circle announced official Poloniex mobile apps for iOS and Android. On Jul 27 Circle announced delisting of 9 coins from Poloniex that led to a loss of 23-81% of their value same day. Sad reminder about how much a project can depend on a single centralized exchange. DCR supply and market cap is now correct on onchainfx.com and finally, on coinmarketcap.com. Thanks to @sumiflow, @jz and others doing the tedious work to reach out the various websites.
About This Issue
[Help!] Transfer funds without syncing Bitcoin Core
Hello guys, Here is what happened. I have done a small freelancing work, and the guy asked whether to pay in Bitcoins. Having never owned Bitcoins, I said YES. I quickly fired up to bitcoin.org and there I was asked to choose a wallet. Selected the first entry in the list of things, which is Bitcoin Core ,downloaded and installed. I then created an address to receive funds, and sent it across. Which I was confirmed that went successfully. https://blockchain.info/address/39UM5DMztcEmP2RoBiHJfArhuVuSv3Ndcj Then I switched back to Bitcoin Core, to check if the transaction really went through; here I am seeing it is downloading a HUGE set of files. Having only a capped amount of data, I quickly disabled syncing. 150GB is a half a year worth of data for me. To obtain the funds without syncing, I have tried few things with no luck yet;
Transferring private key to blockchain.info (Import succeeds but 0.0 balance)
Transferring private key to Electrum using import sweep (Gives error "No inputs found. (Note that inputs need to be confirmed" ) )
Making a transaction to another account using command line. (I have used this article, but unable to broadcast the transaction. Most probably due to my address being multi signature wallet. )
Is there anyone who can point me in the right direction? Thanks. ---------------------------------------------------------------------------- Update: SOLVED! As u/Hodlini , u/MrRGnome and u/BobAlison suggested, what was missing was the "p2wpkh-p2sh:" prefix when importing to Electrum. Since I have entered my private key in many places while figuring things out, I have moved funds to a separate wallet; just to be safe. :) Thanks all for pointing me in the right direction!
Final version 1.3.0 of the core software was released bringing all the enhancements reported last month to the rest of the community. The groundwork for SPV (simplified payment verification) is complete, another reduction of fees is being deployed, and performance stepped up once again with a 50% reduction in startup time, 20% increased sync speed and more than 3x faster peer delivery of block headers (a key update for SPV). Decrediton's integrations of SPV and Politeia are open for testing by experienced users. Read the full release notes and get the downloads on GitHub. As always, don't forget to verify signatures. dcrd: completed several steps towards multipeer downloads, improved introduction to the software in the main README, continued porting cleanups and refactoring from upstream btcd. Currently in review are initial release of smart fee estimator and a change to UTXO set semantics. The latter is a large and important change that provides simpler handling, and resolves various issues with the previous approach. A lot of testing and careful review is needed so help is welcome. Educational series for new Decred developers by @matheusd added two episodes: 02 Simnet Setup shows how to automate simnet management with tmux and 03 Miner Reward Invalidation explains block validity rules. Finally, a pull request template with a list of checks was added to help guide the contributors to dcrd. dcrwallet: bugfixes and RPC improvements to support desktop and mobile wallets. Developers are welcome to comment on this idea to derive stakepool keys from the HD wallet seed. This would eliminate the need to backup and restore redeem scripts, thus greatly improving wallet UX. (missed in July issue) Decrediton: bugfixes, refactoring to make the sync process more robust, new loading animations, design polishing. Politeia: multiple improvements to the CLI client (security conscious users with more funds at risk might prefer CLI) and security hardening. A feature to deprecate or timeout proposals was identified as necessary for initial release and the work started. A privacy enhancement to not leak metadata of ticket holders was merged. Android: update from @collins: "Second test release for dcrandroid is out. Major bugs have been fixed since last test. Latest code from SPV sync has been integrated. Once again, bug reports are welcome and issues can be opened on GitHub". Ask in #dev room for the APK to join testing. A new security page was added that allows one to validate addresses and to sign/verify messages, similar to Decrediton's Security Center. Work on translations is beginning. Overall the app is quite stable and accepting more testers. Next milestone is getting the test app on the app store. iOS: the app started accepting testers last week. @macsleven: "the test version of Decred Wallet for iOS is available, we have a link for installing the app but the builds currently require your UDID. Contact either @macsleven or @raedah with your UDID if you would like to help test.". Nearest goal is to make the app crash free. Both mobile apps received new design themes. dcrdata: v3.0 was released for mainnet! Highlights: charts, "merged debits" view, agendas page, Insight API support, side chain tracking, Go 1.11 support with module builds, numerous backend improvements. Full release notes here. This release featured 9 contributors and development lead @chappjc noted: "This collaboration with @raedahgroup on our own block explorer and web API for @decredproject has been super productive.". Up next is supporting dynamic page widths site wide and deploying new visual blocks home page. Trezor: proof of concept implementation for Trezor Model T firmware is in the works (previous work was for Model One). Ticket splitting: updated to use Go modules and added simnet support, several fixes. docs: beginner's guide overhaul, multiple fixes and cleanups. decred.org: added 3rd party wallets, removed inactive PoW pools and removed web wallet. @Richard-Red is building a curated list of Decred-related GitHub repositories. Welcome to new people contributing for the first time: @klebe, @s_ben, @victorguedes, and PrimeDominus! Dev activity stats for September: 219 active PRs, 197 commits, 28.7k added and 18.8k deleted lines spread across 6 repositories. Contributions came from 4-10 developers per repository. (chart)
Hashrate: started and ended the month around 75 PH/s, hitting a low of 60.5 and a new high of 110 PH/s. BeePool is again the leader with their share varying between 23-54%, followed by F2Pool 13-30%, Coinmine 4-6% and Luxor 3-5%. As in previous months, there were multiple spikes of unidentified hashrate. Staking: 30-day average ticket price is 98 DCR (+2.4). The price varied between 95.7 and 101.9 DCR. Locked DCR amount was 3.86-3.96 million DCR, or 45.7-46.5% of the supply. Nodes: there are 201 public listening nodes and 325 normal nodes per dcred.eu. Version distribution: 5% are v1.4.0(pre) dev builds (+3%), 30% on v1.3.0 (+25%), 42% on v1.2.0 (-20%), 15% on v1.1.2 (-7%), 6% on v1.1.0. More than 76% of nodes run v1.2.0 and higher and therefore support client filters. Data as of Oct 1.
Obelisk posted two updates on their mailing list. 70% of Batch 1 units are shipped, an extensive user guide is available, Obelisk Scanner application was released that allows one to automatically update firmware. First firmware update was released and bumped SC1 hashrate by 10-20%, added new pools and fixed multiple bugs. Next update will focus on DCR1. It is worth a special mention that the firmware source code is now open! Let us hope more manufacturers will follow this example. A few details about Whatsminer surfaced this month. The manufacturer is MicroBT, also known as Bitwei and commonly misspelled as Bitewei. Pangolinminer is a reseller, and the model name is Whatsminer D1. Bitmain has finally entered Decred ASIC space with their Antminer DR3. Hash rate is 7.8 TH/s while pulling 1410 W, at the price of $673. These specs mean it has the best GH/W and GH/USD of currently sold miners until the Whatsminer or others come out, although its GH/USD of 11.6 already competes with Whatsminer's 10.5. Discussed on Reddit and bitcointalk, unboxing video here.
@matheusd started tests on testnet several months ago. I contacted him so we could integrate with the pool in June this year. We set up the machine in July and bought the first split ticket on mainnet, using the decredbrasil pool, on July 19. It was voted on July 30. After this first vote on mainnet, we opened the tests to selected users (with more technical background) on the pool. In August we opened the tests to everyone, and would call people who want to join to the #ticket_splitting channel, or to our own Slack (in Portuguese, so mostly Brazilian users). We have 28 split tickets already voted, and 16 are live. So little more than 40 split tickets total were bought on decredbrasil pool. (@girino in #pos-voting)
KuCoin exchange listed DCBTC and DCETH pairs. To celebrate their anniversary they had a 99% trading fees discount on DCR pairs for 2 weeks. Three more wallets integrated Decred in September:
Atomic desktop wallet added Decred in version 0.1.31. The team answered many questions on Reddit.
AnyBit wallet added Decred. It features built-in price and news tracking. Notably, the source code is open for their Android and iOS wallets.
Coboadded Decred support into their Android and iOS wallets.
ChangeNow announced Decred addition to their Android app that allows accountless swaps between 150+ assets. Coinbase launched informational asset pages for top 50 coins by market cap, including Decred. First the pages started showing in the Coinbase app for a small group of testers, and later the web price dashboard went live.
The birth of a Brazilian girl was registered on the Decred blockchain using OriginalMy, a blockchain proof of authenticity services provider. Read the full story in Portuguese and in English.
Advertising report for September is ready. Next month the graphics for all the ads will be changing.
Marketing might seem quiet right now, but a ton is actually going on behind the scenes to put the right foundation in place for the future. Discovery data are being analyzed to generate a positioning strategy, as well as a messaging hierarchy that can guide how to talk about Decred. This will all be agreed upon via consensus of the community in the work channels, and materials will be distributed. Next, work is being done to identify the right PR partner to help with media relations, media training, and coordination at events. While all of this is coming up to speed, we believe the website needs a refresher reflecting the soon to be agreed upon messaging, plus a more intuitive architecture to make it easier to navigate. (@Dustorf)
Raedah Group went on the streets of Portland, USA with a pretty blue tent. (photos)
Meetup at Binzantin Cafe in Taipei, Taiwan. @morphymore: "There were 20-ish attendees, and about half of them have joined the Chinese FB group. Most of them don't hear about Decred before, but have expressed the interest in learning more about it after the event. Overall, it's a good exposure for Decred in the Taiwan community.". A report with photos was posted on Facebook, more photos are here and here.
@joshuam made a Decred Jacket appearance at Singapore Grand Prix. (photos)
NewTech PDX meetup in Portland, USA. Raedah Group presented Decred and reported "lots of new converts". (photos)
North Shore Bitcoin & Blockchain in Glenview, USA. @dustorf gave a five minute overview of Decred and noted: "There were only about 25 people, but about 1/3 of them were aware of Decred prior. (...) Our simple presence and explanation of the project moved opinion from 'another shitcoin they sold after mining' to 'an interesting and viable project worthy of further investigation'.". (photos: 12)
Bitcoin Meetup CDMX in Mexico City on Oct 6. @elian will be talking about Decred at the oldest Bitcoin meetup in Mexico.
SF Blockchain Week in San Francisco, USA on Oct 9. @lukebp will discuss DPoS vs PoS on a panel 9:30a-10:15a at the Titans of Tech Stage, Hilton Union Square.
Decred Meetup in Casablanca, Morocco on Oct 27. @butterfly will host the event and talk about Decred in French.
Texas Bitcoin Conference Austin, USA on Oct 27-28. @BAB: "The great thing about this is that it will also be a Decred Summit. We will have half of the conference dedicated to Decred topics, updates, etc."
Websummit in Lisbon, Portugal on Nov 5-8. @moo31337 will be on a panel discussing "2018: A Rollercoaster Year for Cryptocurrencies"
We'll begin shortly reviewing conferences and events planned for the first half of 2019. Highlights are sure to include The North American Bitcoin Conference in Miami (Jan 16-18) and Consensus in NYC (May 14-16). If you have suggestions of events or conferences Decred should attend, please share them in #event_planning. In 2019, we would like to expand our presence in Europe, Asia, and South America, and we're looking for community members to help identify and staff those events. (@Dustorf)
August issue of Decred Journal was translated to Russian. Many thanks to @DZ! Rency cryptocurrency ratings published a report on Decred and incorporated a lot of feedback from the community on Reddit. September issue of Chinese CCID ratings was published (snapshot), Decred is still at the bottom. Videos:
The underbelly of blockchain Governance - fiat licensing and our code with Marco Peerboom and Chris DeRose (youtube, tweet, decred, missed in August issue) Insightful dialogue about men's underwear, licenses, subtleties of GPL, BSD wars, tiling window managers and much more.
Introduction to Decred (Korean, youtube) @Killawhale collected a lot of feedback from the community and produced this video to spread the word in Korea.
Perspectives on Governance from Nathan Wilcox, Jonathan Zeppettini, Vitalik Buterin (z.cash)
Decred - an example of governance (Portuguese, youtube)
Decred, the crypto that wants to compete with Bitcoin (French, youtube)
Exodus.io Live with Marco from Decred! (youtube) Marco joins Exodus.io to discuss what makes DCR an asset that will stand the test of time.
Building Decred With Systems Development Lead Marco Peereboom - Governance, Politeia, Lightning (youtube) Topics: early days, Politeia, the structure of Decred, dcrtime, Lightning Network, attracting users and developers, future plans (DEX, Schnorr signatures, privacy, DAEs).
Decentralized autonomous funding of blockchain projects by @Richard-Red (medium, discussion on decred and dashpay)
The trouble with infrastructure, "thin" protocols in particular, is that someone has to build them at a cost. e.g. LN takes a ton of work, doesn't necessarily generate value itself, but it magnifies the value of BTC or whatever coin that uses it. I see the DEX in a similar light - whoever creates it is not going to make a bunch of money from it, but it will magnify the value of the underlying asset(s) that end up having a deep order book on the DEX. (@jy-p in #dex)
Twitter: why decentralized governance and funding are necessary for network survival and the power of controlling the narrative; learning about governance more broadly by watching its evolution in cryptocurrency space, importance of community consensus and communications infrastructure. Reddit: yet another strong pitch by @solar; question about buyer protections; dcrtime internals; a proposal to sponsor hoodies in the University of Cape Town; Lightning Network support for altcoins. Chats: skills to operate a stakepool; voting details: 2 of 3 votes can approve a block, what votes really approve are regular tx, etc; scriptless script atomic swaps using Schnorr adaptor signatures; dev dashboard, choosing work, people do best when working on what interests them most; opportunities for governments and enterprise for anchoring legal data to blockchain; terminology: DAO vs DAE; human-friendly payments, sharing xpub vs payment protocols; funding btcsuite development; Politeia vote types: approval vote, sentiment vote and a defund vote, also linking proposals and financial statements; algo trading and programming languages (yes, on #trading!); alternative implementation, C/C++/Go/Rust; HFTs, algo trading, fake volume and slippage; offline wallets, usb/write-only media/optical scanners vs auditing traffic between dcrd and dcrwallet; Proof of Activity did not inspire Decred but spurred Decred to get moving, Wikipedia page hurdles; how stakeholders could veto blocks; how many votes are needed to approve a proposal; why Decrediton uses Electron; CVE-2018-17144 and over-dependence on single Bitcoin implementation, btcsuite, fuzz testing; tracking proposal progress after voting and funding; why the wallet does not store the seed at all; power connectors, electricity, wiring and fire safety; reasonable spendings from project fund; ways to measure sync progress better than block height; using Politeia without email address; concurrency in Go, locks vs channels. #support is not often mentioned, but it must be noted that every day on this channel people get high quality support. (@bee: To my surprise, even those poor souls running Windows 10. My greatest respect to the support team!)
In September DCR was trading in the range of USD 34-45 / BTC 0.0054-0.0063. On Sep 6, DCR revisited the bottom of USD 34 / BTC 0.0054 when BTC quickly dropped from USD 7,300 to 6,400. On Sep 14, a small price rise coincided with both the start of KuCoin trading and hashrate spike to 104 PH/s. Looking at coinmarketcap charts, the trading volume is a bit lower than in July and August. As of Oct 4, Decred is #18 by the number of daily transactions with 3,200 tx, and #9 by the USD value of daily issuance with $230k. (source: onchainfx) Interesting observation by @ImacallyouJawdy: while we sit at 2018 price lows the amount locked in tickets is testing 2018 high.
ASIC for Lyra2REv2 was spotted on the web. Vertcoin team is preparing a new PoW algorithm. This would be the 3rd fork after two previous forks to change the algorithm in 2014 and 2015. A report titled The Positive Externalities of Bitcoin Mining discusses the benefits of PoW mining that are often overlooked by the critics of its energy use. A Brief Study of Cryptonetwork Forks by Alex Evans of Placeholder studies the behavior of users, developers and miners after the fork, and makes the cases that it is hard for child chains to attract users and developers from their parent chains. New research on private atomic swaps: the paper "Anonymous Atomic Swaps Using Homomorphic Hashing" attempts to break the public link between two transactions. (bitcointalk, decred) On Sep 18 Poloniex announced delisting of 8 more assets. That day they took a 12-80% dive showing their dependence on this one exchange. Circle introduced USDC markets on Poloniex: "USDC is a fully collateralized US dollar stablecoin using the ERC-20 standard that provides detailed financial and operational transparency, operates within the regulated framework of US money transmission laws, and is reinforced by established banking partners and auditors.". Coinbase announced new asset listing process and is accepting submissions on their listing portal. (decred) The New York State Office of the Attorney General posted a study of 13 exchanges that contains many insights. A critical vulnerability was discovered and fixed in Bitcoin Core. Few days later a full disclosure was posted revealing the severity of the bug. In a bitcointalk thread btcd was called 'amateur' despite not being vulnerable, and some Core developers voiced their concerns about multiple implementations. The Bitcoin Unlimited developer who found the bug shared his perspective in a blog post. Decred's vision so far is that more full node implementations is a strength, just like for any Internet protocol.
About This Issue
This is the 6th issue of Decred Journal. It is mirrored on GitHub, Medium and Reddit. Past issues are available here. Most information from third parties is relayed directly from source after a minimal sanity check. The authors of Decred Journal have no ability to verify all claims. Please beware of scams and do your own research. Feedback is appreciated: please comment on Reddit, GitHub or #writers_room on Matrix or Slack. Contributions are also welcome: some areas are adding content, pre-release review or translations to other languages. Credits (Slack names, alphabetical order): bee, Dustorf, jz, Haon, oregonisaac, raedah and Richard-Red.
Today I have finally accepted, that due to my stupidity, I have lost 1 BTC. I want to share this with you all.
How I learned about Bitcoin
In early 2013 is when I first learned of Bitcoin. I remember sitting in my barracks room, debating whether or not buy a coin. Didn't really know to much about what Bitcoin was, but it sounded promising. I remember the cost of once coin being roughly $75. "Wow, that's a lot to spend on something I will never be able to touch. I think I'll pass." As time went on, I would see Bitcoin in the news, or discussed on Reddit, but didn't give it a second thought, until this summer.
How I started Bitcoin
I was on Reddit when someone mentioned the dark net market Alpha Bay. The dark net and Tor browsing and cryptocurrency sparked my interest as I tried to learn as much as I could. I had just gotten out of the Marine Corps and was working at a Boy Scout Camp, trying to absorb as much information as I could using only my slow data speeds. Around August, I bought some coin. Not a lot, maybe .001BTC. Looking back now, I was addicted to it. I loved watching it go up. I even loved watching it go down. It was new and it was fascinating. I posted in this subreddit a few times, asking questions and learning. Purchasing on coinbase, I would then transfer the BTC I had acquired to an Electrum Wallet on my laptop. Wanting to help the network, I downloaded Bitcoin Core unto my desktop, spend the weeks letting the block chain sync, and this is where I made my error. Once Bitcoin Core had synced, I set my wallet encryption up. I didn't want to use anything I had used before, so I used essentially a song (I didn't but I'm using this as an example). I made my passphrase "somebody once told me the world is gonna roll me" and began consolidating my BTC into this wallet. One day, I decide that this passphrase is too long for me, and changed it to essentially "sotmtwisrm". On Thursday November 23rd, 2017, Thanksgiving, I made my final $1,500 purchase that finally got me to 1.03 BTC and transferred it to my Bitcoin Core. I now owned a whole Bitcoin. I spent roughly $5,500 to own it, and it was worth $8,000. I was ecstatic. Late that night, I decided that I didn't trust my computer. I would buy a Ledger Nano S. Went to their website and said to myself "Sweet. I can buy this using my Coin!" If you would have asked me if I knew my password, I would have said "Yes. 100% I know it. I would bet a whole coin on it!" and in a way, I did bet a whole coin. My whole Bitcoin. But Bitcoin Core, told me otherwise. And I panicked. I typed, and retyped, and tried everything I could. But the wallet, was staying shut. I went to my safe, opened it up and pulled out the index card that said "Bitcoin Core" on it. I had put it next to the other information for my girlfriend, in case something happens to me. The card was blank. I never wrote it down. I lost, a whole Bitcoin.
How do I feel?
I feel like a part of me has been ripped out.No one takes losing $6,000 lightly. I tell myself that money is just money, but it still hurts. I didn't sleep at all that night. I was stupid. While in the Corps, I saved my money and lived my life frugally, I saved up a good nest egg for now, while I attend college, and I pissed a good chunk of it away in a few weeks. I have contacted davebitcoin with www.walletrecoveryservices.com in an attempt to get it back, so hopefully he'll be able to help me. I have also been attempting to Brute Force on my own desktop with what I know, but am not putting much faith in it. I have written it off.
Moral of the story
Please. For the love of all that is holy, write your passphrase and passwords down. Multiple locations. Backup your wallet. It's your wallet, its your money, it's your Bitcoin. YOU are the bank! Secure yourself, before you wreck yourself.
[How To]Full Node (Beta) + GUI + Staking on Raspberry PI 3
Hello everyone, With the Full Node Beta recently being released on 3/28 and the Full Node GUI on 4/11, I thought it would be an excellent time to update the RPi tutorial by olcko and demon for the RPi. I've been running it now for about 1 week and it has been working great so far, but I haven't been connected to many peers running the full node. Hopefully this tutorial will help change that! This tutorial will take over from the previous tutorial's step 4. Steps 1-3 cover installing Raspbian and SSH on the RPi and are excellent. PREREQUISITES
git clone https://github.com/stratisproject/StratisBitcoinFullNode.git cd StratisBitcoinFullNode git submodule update --init --recursive cd src restore build cd Stratis.StratisD run -apiuri=http://0.0.0.0:32771 The "apiuri" option enables access to the API from another device on your network (Thanks Daan Damhuis!). That's it! Your node should be running now, but may take a while to sync. You can test the node's API by pointing your browser to http://:37221/swagge If you don't plan on using RPC, make sure you follow the instructions from the previous tutorial step 3 to block RPC connections. sudo ufw deny 16174 Full Node GUI Setup Now that the Core Daemon is running, we can install the GUI frontend. We will be following the instructions from here. The GUI that interacts with the node can be installed on the RPi or another device on your network (with some tweaks to the underlying code, below). cd ~/StratisFullNode git clone https://www.github.com/stratisproject/FullNodeUI cd FullNodeUI/FullNodeUI.UI npm run mainnet That's it! Go ahead and set up your new wallet! Remote GUI Tweaks I'm adding this section for RPi owners who don't run a GUI on their RPi device, but may want to run the GUI on another device on their network. This can be done because the GUI interacts with the full node through the API; however it will take some tweaks to the code before compiling to make this set-up work. The instructions for "Full Node GUI Setup" above should be run on that device. There is one place in the code where you need to replace "localhost" with your RPi's local private network IP address.
this.stratisApiUrl = 'http://:' + this.apiPort + '/api'; You will also need to comment out a few sections to prevent the GUI from starting up or shutting down the full node when you open/close the GUI.
//closeStratisApi(); Helpful RPi tips for remote management
Use Screen + SSH! Screen is a wonderful utility that will leave your session running when you disconnect from ssh. This is available via sudo apt-get install screen on your RPi. You can reconnect when you return at another ssh session with:
Sometimes the full node on your RPi will hang or unexpectedly crash - stopping staking in the process. Borrowing from here, I have created a script that will monitor for hangs or crashes and restart the node.
If the node is restarted, you will still need to re-enable staking. This can be accomplished through the GUI, a browser using swagger, or with an API call through a local script (insecure).
Sample helper scripts, including a .screenrc configuration, for the above can be found in a pastebin here. Example API calls can be found on the full node's swagger API interface.
Note: your wallet passphrase must be sent via POST to re-enable staking.
I hope you found this helpful! Please feel free to message me with questions/errors/improvements or find me on the discord/telegram as @TjadenFroyda. I'll update this post with feedback. Donations are welcome as well: SNSwQVvB5FB6KPVT7325tJGWXbxVd4xceR
Let me start by saying I am a huge fan of cryptos and have been for over 5 years now. Everyone keeps saying Ethereum is the future and I appreciate the technology gains made by the blockchain but it seems like the wallets are very technical. I have both geth and parity and neither one will sync past about 50% of the blockchain. it doesnt matter how i boot it with run cmd it will always stop about 8 hours in.I have left it on for 3 days and its on the same block. Fast sync should not take that long. The point of this is i have mined bitcoin and dogecoin and know a decent amount about computers however I cant even get a full node up and running for ethereum. if there is going to be a future for ethereum they need a very simple user interface like blockchain.info did and also the bitcon core wallet. There isnt even a simple wallet to download for ethereum because of all the geth and wallet errors. parity has been equally problematic. I dont use chrome so metamask is out. Where do I go from here? Is there a simple downloadable User Interface for Ethereum to simply send and recieve and hold my own private keys (not coinbase)? because the 2 options out right now are complete trash. parity is trash. ethereum wallet is trash. i can sync the full chain on geth but then the wallet cant see geth and shows no sync. all my time settings are correct. Etherum in my eyes has to be made user friendly. Its simple business. You shouldn't have to run cmd line options when booting a program to make it work properly. I bet over 80% of users that want to try ethereum can't because of wallet and technical issues. Let me know what you folks think. Maybe I am missing something but the 5 people I have asked have all said they couldnt get their wallet running so they said screw it and went back to btc.
IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018
[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC [16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A. [16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started. [16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet? [16:03] <@Tron> Sure. [16:03] can someone volunteer to take notes and post also? [16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778 [16:04] <@Tron> It looks back 180 blocks to calculate the diff. [16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does. [16:04] I'll save a log of the whole meeting and can post it on the subreddit thread. [16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries. [16:04] great [16:05] <@Wolfsokta> We plan to release the binaries later today. [16:05] @Tron have you looked into the timestamp attack concerns of DGW? [16:05] https://github.com/zawy12/difficulty-algorithms/issues/30 [16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks. [16:06] <@Tron> Moved from 2h to 12 minutes. [16:06] nice [16:06] Oh wow okay [16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks. [16:07] why would 2h ever be acceptable? lol [16:07] 2h was originally used for daylight savings shenanigans I believe [16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time. [16:07] makes sense [16:08] what about the segmentation fault when reindexing? [16:08] any fix yet? [16:08] @Tron 12 minutes seems to be pretty small window for clock skew [16:08] I assume it was chosen due to 1/10th scaling from BTC? [16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit. [16:09] <@Tron> We did divide existing by 10. [16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet? [16:10] What block is it activating on mainnet? [16:10] <@Wolfsokta> 338778 [16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)? [16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo. [16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet. [16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo [16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain. [16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though. [16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right. [16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works. [16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked. [16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly. [16:14] Are there any issues or comments on the DGW code that should be addressed? [16:14] @devs in general [16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge. [16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right? [16:16] because of the 12 minute timestamp thing? [16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited. [16:17] nice [16:17] @russki Yeah, pretty much. [16:17] verge is a different type of situation - but overall asics and mining are a risk always [16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change? [16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added. [16:19] ooh yeah i saw those github commits [16:19] looking good [16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT [16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/ [16:20] nice [16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z [16:20] <@Tron> We'll post a FAQ on assets later today. [16:21] <@Wolfsokta> And it only is 100 Raven for a subasset [16:21] on testnetv4 it still says asset activation status: waiting [16:21] why? [16:21] <@Tron> Yep, it needs to be voted in. [16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better. [16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through. [16:21] ok nice [16:22] <@Wolfsokta> Any questions about subassets? [16:23] are they unique? [16:23] <@Tron> No [16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset. [16:23] <@Tron> Maybe I misunderstood the question. Unique with parent. [16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50? [16:23] yes [16:23] oooh ok that makes more sense [16:23] <@Wolfsokta> Exactly thanks traysi [16:24] <@Tron> And, not the same thing as "Unique Assets" [16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase. [16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT [16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them? [16:25] <@Tron> Yes [16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere? [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:25] satoshi corbie @russkidooski [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:26] <@Tron> Sub-assets are identical to assets after creation. [16:26] <@Tron> Just cheaper to create, and in your "owned" namespace. [16:26] Okay cool [16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1 [16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly. [16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue [16:26] How much is it going to be for a sub-asset? [16:27] 100 [16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under. [16:28] do you know what the issue was? [16:28] <@Wolfsokta> It seems to be a build problem with the boost library. [16:28] Still looking into though. :) [16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3 [16:29] yea i get the same issue on windows 10 [16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB [16:30] static compiled on ubuntu 18.04 [16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test. [16:30] @Trap we will look into that also [16:30] no problem, im just curious lol [16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue. [16:32] <@Tron> We're dropping Windows support ;) [16:32] lol [16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it. [16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue. [16:34] what did you guys do to fix the linux version? [16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement [16:34] The issue has been fixed on Linux and Mac though? [16:34] (oops sorry already answered) [16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found. [16:34] Built the binairies on a Ubuntu 16.04 box. [16:34] that was it? [16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue. [16:35] is there a boost 1.58 repo on 18.04? [16:35] 18.04 used 1.65*** [16:36] I've built with boost 1.68 on arch Linux [16:36] It worked [16:37] wallet 2.0.x? [16:37] @Trap, the issue is when -reindex is used. [16:37] Oh sorry my bad [16:37] Wallet 2.0.3 [16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208 [16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04 [16:39] Any other questions pertaining to the segfault? [16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting. [16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join [16:42] Yea. It is very hard to read this back. [16:42] Also no message history [16:42] If you disconnect and reconnect [16:42] <@Tron> I'll throw in a vote for Discord. [16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad. [16:43] Some of us used a VPN before we connected to IRC [16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A [16:43] https://www.strawpoll.me/16247952 [16:43] poll [16:43] Make a discord when only mods can submit links [16:43] Where* [16:45] Discord won the poll 5 to 2 [16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings. [16:45] we know [16:46] <@Wolfsokta> We also want any developer to be able to speak. [16:48] <@Wolfsokta> We're open to try Discord next week. [16:48] <[kai]> perhaps you could even get a feed from this irc to discord? [16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here. [16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working? [16:50] <[kai]> https://github.com/reactiflux/discord-irc [16:50] <[kai]> im sure you could make this a one way deal. [16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord. [16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week. [16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins. [16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield? [16:54] <[kai]> DGW solution seems solid. [16:55] <[kai]> was just curious if it was one of the four solutions you looked at. [16:55] <@Wolfsokta> Tron is answering... Any others Q? [16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA. [16:55] <[kai]> right on. [16:56] <[kai]> cheers guys, see you next time. [16:56] OPen the gates for the last 4 minutes for any other questions? [16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request. [16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community. [16:59] ^ 6:59] You devs are pretty cool [16:59] did the burn get discussed? [16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice. [17:00] <@Tron> Thanks everyone!
A guide to sign a super bitcoin (SBTC) transaction offline with patched Electrum for paranoid. Supports any wallets supported by Electrum (including segwit-p2sh and bech32 and all BIP39 seeds). Later BCD will be added.
This is quite advanced. This guide assumes you have some basic experience with the command line, can run Linux and you understand the basics of keys/signing/broadcasting transactions. And that you can compile and run Bitcoin Core and run Electrum. Also, some JSON experience is also nice. Move you bitcoins to safe addresses first. It is best to use a new seed. Although the procedure in this guide is safe even for hot addresses (containing bitcoins), there is always a risk of a critical mistake. So play it safe. Why such a guide? I followed these steps because I did not want to expose the keys to any online machine at all. Even if the keys do not have any bitcoins, you can some day have bitcoins sent to these addresses or you have a fork that you have not claimed. All can be stolen if you exposed your key. This procedure should work with everything that Electrum supports (except maybe F2A that may be not supported on the SBTC chain), so Electrum seed legacy or segwit, LedgeTrezor with legacy or segiwt-p2sh (m/'49) derivation. Similarly, any BIP39 seeds or a single key. are also fine.
Apply my patch patch -P0 also this article. The guide assumes that you use patched Electrum from now on.
Run the patched Electrum and catch up with your wallets you want to claim (the wallets can and rather should be watch only, or on ledgetrezor, otherwise your keys are exposed). Now go offline or set localhost as your server that Electrum connects to so no connection is performed. It's required so Electrum will not update the wallet after you edit it.
You can manually create a transaction from the command line but you can use Electrum GUI. You need to locate the wallet file and remove all the transactions from the wallet file except for the one that funds the address you want to claim (the wallet obviously must not be encrypted but for watch-only this is OK). This is tricky. You need to make sure, you gave a proper JSON file, so all the final commas must be dropped. So "addr_history":, "transactions": , "tx_fees":, "txi", "txo", and "verified_tx3": should only contain the funding transaction(s), i.e. the one that you want to spend from.
Run Electrum and check if the wallet is OK. Electrum will show an error if not. You will probably make a few errors so go back to editing the wallet.
Compile it and let it sync the blockchain (it will take a long time). Run it it with as large -dbcache= as you can. If you have a Bitcoin blockchain you can copy the blocks up to the fork date and issue sbtcd with -reindex. It will just reindex them and it will be faster.
Generate a sbtc address with sbtc-cli getnewaddress. You can skip this step and send directly to an exchange but this intermediate step is safer.
Create a transaction in Electrum to this address. Select all the bitcoins and use as small fee as possible (SBTC blocks are empty so any fee above 1 SBTCsat/byte should be OK).
Save the transaction to a pendrive
Download and install Kubuntu 16.04 (Kubuntu has all the QT libraries for Electrum) on a pen drive.
Copy patched Electrum and the save the transaction to a pen drive (separate from Kubuntu will be more convenient).
Run Kubuntu from the USB without any network access. Run Electrum from the pendrive. Create a wallet from the seed or private keys. The wallets are stored in RAM so after you reboot the computer, they will be gone. Load the transaction, sign it and save it to the pen drive.
Go back to the SBTC Core on the online machine. Display the raw transaction (starts with the hex=). Check in the SBTC Core if it is correct sbtc-cli decoderawtransaction hex
If it looks fine (and your blockchain got synced), broadcast it sbtc-cli sendrawtransaction hex
If there is no error, congratulations, you sent the transaction to the specified address. If it is to your SBTC Core wallet, wait until it confirms and send it further with sbtc-cli setfee feeperkb sbtc-cli sendtoaddress "addr" value "" "" true true I'm going to update this guide when I figure out the BCD transactions intrinsics. You can download and run the BitcoinDiamond Core clone in the meantime. SBTC tips: 1KjuY8CTrwMhdLt3uF3hCcSgfkHMyo1ELf
[Tutorial] Creating a XMG specific, secure, air-gapped, Cold Storage Address/Wallet
Forward This is a tutorial about securing an XMG wallet in an air-gapped, cold storage manner. Before you begin and, if you choose to proceed, while you are doing the steps, take a moment to be aware of what you are doing. This method is ultra secure and is based on a method that has been used to protect millions in BTC and other coins. But all that aside, part of this method is maintaining physical access to encrypted files, maybe for months or years ... keep this in mind and alter the method's storage options to suit your unique situation. In other words, try your best not to become this guy. The Who, What, and Why? Protecting your cryptocurrency is a very important step when you enter the world of crypto. There are dozens of way to do this, with varying levels of security and varying levels of acceptance across the mainstream coins as well as the altcoins. Obviously, Bitcoin (BTC) is the primary coin upon which the value of all other altcoins are based, but it is also the main coin for which security protocols are developed. But just because you don't own 20BTC with a value of $200,000.00 doesn't mean you shouldn't get into the habit of securely handling your wallet contents and investments, which includes Magi Coin. One of the better way of securing crypto is placing those coins into a cold storage that is "air-gapped" from the internet. Air-gapped systems are computer systems, or specially designed devices, that are completely disconnected from the internet. This protects against outside actors being able to access anything you store behind the air-gap. If nothing is ever detected, then no one would ever know it exists. There is a saying in the crypto community ... "if you don't have the key to your coins, then you don't own them according to the blockchain." This includes coins in Bittrex, Coinbase, GDAX, etc. If you can't send and receive the coin at will, or you don't own the key to where your coins are stored, then you don't own it ...period. As it is said, while inaccurate in real law, is totally applicable here, possession is 9/10ths of the law. These methods not only give you, and ONLY you, the keys to your coins but also protects them from company hacks, fraud, bad faith actions, and simple electronic glitches. There are several pre-made products that allow storage of various coins, but your personal choice of altcoin might not have implemented support for these devices. As an example, a few of the more well known devices are the Ledger S Nano and the TREZOR. While dedicated devices are one solid way to secure your crypto, they can also be very expensive. I mean, $70.00-100.00 USD can buy a lot of XMG! With these things in mind, this tutorial is one way to create a protected "cold storage," off-line*, m-wallet to help protect your investment. If followed, as is, when you finish this tutorial you should have a minimum of two local digital copies of a cold storage wallet for your XMG, as well as one (or more) copies stored in the cloud server of your choice.
Please note, coins stored in an offline wallet, while are exceedingly safe, will not stake. Take this into consideration when making decisions about this, or other, protected storage options.
Getting Started: Cloud Storage Setup (Optional and can be completed after the main instructions) If you decide to use a cloud storage like Google or Amazon, or even a local homebrew like Nextcloud, you need to make sure that access to said cloud drive is secure. You do this by signing up for a new account, using a username that you only use with that single service and a password that is a string of random words or a phrase. If two-factor authentication is available, use it. If using random words for your "phrase", take a dictionary, and turn to random pages. While on these pages, close your eyes and put your finger on the page. The word your finger is closest too is the word you write down. Repeat this 10-12 times. If using a phrase from a book, make sure it is something you will be able to remember, and it should be a minimum of 18 words long. Write it down and put it in a safe deposit box if you aren't sure you can remember it. Later, I'll discuss some other novel ways to secure a passphrase. Once this is done, you will log out of the drive and proceed with the next step. Note: This step isn't necessary, there are alternatives to using cloud services that are just as secure, but it is an acceptable option. Creating the air-gapped Cold Storage Wallet (CSA) First, download the m-wallet setup files from m-core.org and copy them to a flashdrive that has been freshly erased and formatted. If you are hyper-vigilant regarding security, secure erase the drive using your regular OS. Then, choose one of the many "Live Operating System" choices out there. This is otherwise known as a "trial" use of the operating system that doesn't involve installing it on your hard drives/SSDs. These are typically images that are burned to a CD/DVD or written to a USB drive, then your computer is booted from this image. The OS creates a RAM-based virtual drive to run from and then uses the USB or CD like a storage device to hold files. When you turn off the computer, any in the RAM is lost, this is where the security comes into play. This allows you to load up an operating system without leaving physical data writes to any physical media. Once you have your USB or CD Live OS, take a computer that is turned off and do the following steps to create the "air-gap" ...
Remove any USB drives (flash, SSD, or HDD) from the computer.
If you can physically remove the network card/dongle, do so.
If you cannot physically remove the network/wifi device and you have a laptop that allows you to physically turn off the Wifi signal, so that instead.
If connected with a network cable, disconnect this from the computer.
Unplug the router that you typically connect to.
Again, if you are hyper-vigilant, use a laptop and drive to some location where there is zero wifi signals and turn off your cell phone prior to going further.
These steps create the "air-gap" between you, the wallet data you will create, the computer, and anything that might identify that you are the owner of the address/wallet we are going to create. Now, start up your live CD/USB, follow the directions and when it is loaded you want to put the flashdrive that is holding the wallet program into the computer. Expand it and install it. When it is installed, start it up and allow it to run. The wallet will not sync, clearly, but what it will do is create a new valid XMG address and the wallet.dat file. Cut and paste the new address into a text file and copy it your flash drive. Now, go through the process of encrypting the wallet, which if done thought the wallet program. Pick a VERY strong phrase, that is completely random, for the encryption protocol. Make it 10-18 words long. DO NOT use the same phase that you used for the Cloud Services if you decided to go that route. Write this passphrase down and put it somewhere safe, without it everything you are doing is pointless, it will be the only way to access your XMG cold storage. Navigate to the location where your OS stores the m-wallet's wallet.dat file and copy it to your flash drive. If you have access to some other device for storage, make a second copy at this time just to be safe. Remember, once we turn the computer off all of this data will disappear forever. You MUST make a copy of the wallet.dat to a secondary device to ensure you still have it when the computer is shut down. Verify twice so you don't cry once! This encrypted wallet.dat and the address you pasted into the text file, is the basis for your cold storage. Sending XMG to the address places it into the blockchain and later, when you decide to access your cold storage, the wallet.dat will sync with the blockchain and show your stored balance. Put a copy of the encrypted wallet.dat file on various drives, put it on the cloud services you signed up for, or burn a copy to a CD and hide it. Some people suggest sending a copy to friends or family, but I disagree. Looking at what bitcoin has done, plus the media it has garnered, asking friends and family to hold copies could alert them to your financial holdings. This could make you a target. If you want to make sure someone knows in the event of your untimely death, put it in a will or a "last wishes" document that explains what the data is and how to decrypt it. One way to store your wallet.dat info, that takes it up a notch, is to buy a special USB drive that includes built in encryption ... that's right, you're encrypting your encrypted file. One of the better ones is the following. Apricorn Aegis Secure Key 3Z $70-75.00 Con: As expensive as a hardware wallet. Pro: Can be used for other sensitive, non-crypto related, files. For myself, I just like to have a solid USB drive designed to withstand a nuclear blast. Well, not really, but it is pretty solid... I use this one. Corsair Flash Survivor Stealth 32GB $20-30.00 Con: Accessible by anyone who has the physical drive (but the wallet.dat file is encrypted, so that part is useless to the person without the passphrase). Pro: Will withstand far more than the average flash drive, you could bury it if you wanted. Note: The links above go to Amazon, they do NOT contain any affiliate links and are merely shown as visual examples. Using the Cold Storage Address (CSA) Simply send coins to the address. As I stated, these coins will not stake, but they are secure from nearly anything when it comes to digital theft. The coins in your CSA will be on the blockchain, but no one can access them without your passphrase AND the wallet.dat file. As such, make sure you keep your passphrase secure as well, keep it in at least three spots that only you know about. These spots could be inside a book, a safe deposit box, or merely glued/written under your desk drawer. You could even take it one step further and encrypt the passphrase with an old school book cipher using a book at the library. This might be overkill, but in a rapidly expanding digital world, old school can often be a great way to keep secrets safe. Thawing your Cold Storage Address (CSA) The process to thaw your CSA is basically the reverse of how you created, however driving to the middle of nowhere isn't required. You can thaw your CSA on your regular computer, or any other computer. The steps are as follows... Before you start, while isn't strictly needed, it is a good idea to disconnect your computer from the internet again and reboot your Live OS. This prevents any digital fingerprints on your regular computer, plus it won't interfere with the m-wallet already installed on your computer (if there is one).
If anyone see any factual errors in this tutorial, please let me know, thanks! If you use this and like it, think about sending a small thank you ... in XMG, of course, and, just FYI, it's going into a CSA. 9SPTXRDT1vWQubDBkFykrFRGoLekgfxADr
Ahhh one of the worst things about Bitcoin.... I have dealt personally with this issue. The first time I ran Bitcoin Core (to use with Bitcoin Armory), I let my computer run for a full day before it finally completed it. This was over a year ago. In case of an offline wallet such as Bitcoin-Qt, you will need to be synchronised/update before you see your wallet balance correctly. The Bitcoin client will download the whole blockchain if it is the first time. Once it has been downloaded and you synchronize daily, it will be much faster to do so. There is an existing answer on this post. This issue tracker is only for technical issues related to bitcoin-core. General bitcoin questions and/or support requests and are best directed to the Bitcoin StackExchange. For reporting security issues, please read instructions at htt... I have same issue on 0.14 BTC wallet,Runtime errors during sync - "Error: Out of memory. Terminating." I had to revert on 0.13.2 which works perfectly. Machine specs: OS - Windows 7 Professional 32bit CPU - Intel Core Quad Q8200 2.33GHz RAM - 4GB Disk size - 640GB HD If you did a full format on Windows or Mac, your hard drive sectors have been completely zeroed out, and your data is lost. Old Wallets. If you want to get into your wallet without waiting for the full bitcoin blockchain to sync, just grab the private key from your wallet. You can do this using the Bitcoin Core API or the pywallet tool below.
TokenPay l Syncing troubleshoot tutorial (wallet.dat)
LEGGIMI READ ME Tutorial - How to correclty sync Electra Wallet / fix sync problem All link: Electra.conf Download: https://goo.gl/LeV5m6 ... How To Connect Two Routers On One Home Network Using A Lan Cable Stock Router Netgear/TP-Link - Duration: 33:19. Richard Lloyd Recommended for you mooncoin wallet sync fix Donate Bitcoins on this addres 1He4sTpbxT4AgbtuwRu7JbHirG8zWLWU4G. Reddcoin Wallet, Sync & Staking Overview in 2018 ... How To Quickly Sync A Wallet with Bootstrap (Litecoin/Bitcoin) - Duration: 2:11. Franklyn ... PRO Wallet Out Of Sync ... PRO Wallet Out Of Sync - Another Solution To Fix - Duration: ... Getting your Private Keys from the Bitcoin Core wallet - Duration: 5:11. Bitcoin Daytrader 40,300 views. 5:11. TRON [TRX] HOW I ...