There you go, it's out there now.
TL;DR. Just give me the bits
Would be great if someone who has the skills & tools could generate us a nice stable MacOS build? Anyone?
Backup your wallet before
using this. You've probably already done that, as I am sure you backup your wallet on a regular basis, right?
Something bad happens, your wallet is destroyed AND you didn't take a backup? Don't blame me.
A lot of stuff has been renamed to 'Myriad' - however there are a couple of exceptions for reasons of compatibility with older existing versions:
- default data directory is still myriadcoin
- config file is still myriadcoin.conf
- daemon is myriadcoind, rpc client is myriadcoin-cli
If you are compiling yourself, please configure with something like this:
CFLAGS="-O2 -fPIC" CPPFLAGS="-O2 -fPIC" ./configure
otherwise you'll probably get some errors later on. Additionally, if your CPU supports SSE2, and most modern CPU's do, use this:
CFLAGS="-O2 -fPIC -DUSE_SSE2" CPPFLAGS="-O2 -fPIC -DUSE_SSE2" ./configure
That will enable the SSE2 version of the Scrypt algorithm. This may reduce the CPU load when syncing the blockchain.
Oh, and there's still some tests that fail if you build and run the testsuite. I've been unable to find the issue, so please, when you fix it, submit a pull request.
A big thanks to cryptapus
for their help in getting this release completed. Obviously we must also thank all of the contributors to the Bitcoin Core project, as that is the base that this is all built upon.
And again thanks to 8bitcoder
for starting Myriad in the first place.
Because this release is based on Bitcoin Core 0.10.0 and upwards, it makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with older versions of Myriad Core or other software:
- Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
- The block index database will now hold headers for which no block is stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.11.2 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes (Borrowed from Bitcoin Core's Release Notes)
Myriad Core now uses 'headers-first synchronization'. This means that we first ask peers for block headers and validate those. In a second stage, when the headers have been discovered, we download the blocks. However, as we already know about the whole chain in advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On recent hardware with a decent network link, it can be as little as 3 hours for an initial full synchronization. You may notice a slower progress in the very first few minutes, when headers are still being fetched and verified, but it should gain speed afterwards.
A few RPCs were added/updated as a result of this: - getblockchaininfo now returns the number of validated headers in addition to the number of validated blocks. - getpeerinfo lists both the number of blocks and headers we know we have in common with each peer. While synchronizing, the heights of the blocks that we have requested from peers (but haven't received yet) are also listed as 'inflight'. - A new RPC getchaintips lists all known branches of the block chain, including those we only have headers for.
RPC access control changes
Subnet matching for the purpose of access control is now done by matching the binary network address, instead of with string wildcard matching. For the user this means that -rpcallowip takes a subnet specification, which can be
- a single IP address (e.g. 18.104.22.168 or fe80::0012:3456:789a:bcde)
- a network/CIDR (e.g. 22.214.171.124/24 or fe80::0000/64)
- a network/netmask (e.g. 126.96.36.199/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address matches one of them.
|0.9.x and before ||0.10.x |
|-rpcallowip=192.168.1.1 ||-rpcallowip=192.168.1.1 (unchanged) |
|-rpcallowip=192.168.1.* ||-rpcallowip=192.168.1.0/24 |
|-rpcallowip=192.168.* ||-rpcallowip=192.168.0.0/16 |
|-rpcallowip=* (dangerous!) ||-rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 188.8.131.52), a network/netmask (e.g. 184.108.40.206/255.255.255.0) or a network/CIDR (e.g. 220.127.116.11/24).
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a possibly vulnerable system. In addition, it can help for (manual) construction of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to importprivkey, but instead takes an address or script (in hexadecimal) as argument. After using it, outputs credited to this address or script are considered to be received, and transactions consuming these outputs will be considered to be sent.
The following RPCs have optional support for watch-only: getbalance, listreceivedbyaddress, listreceivedbyaccount, listtransactions, listaccounts, listsinceblock, gettransaction. See the RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require -txindex, scales better, integrates better with the wallet, and is compatible with future block chain pruning functionality. It does mean that all relevant addresses need to added to the wallet before the payment, though.
It has been observed that many of the RPC functions offered by myriadcoind are "pure functions", and operate independently of the myriadcoind wallet. This included many of the RPC "raw transaction" API functions, such as createrawtransaction.
myriadcoin-tx is a newly introduced command line utility designed to enable easy manipulation of myriad transactions. A summary of its operation may be obtained via "myriadcoin-tx --help" Transactions may be created or signed in a manner similar to the RPC raw tx API. Transactions may be updated, deleting inputs or outputs, or appending new inputs and outputs. Custom scripts may be easily composed using a simple text notation, borrowed from the bitcoin test suite.
This tool may be used for experimenting with new transaction types, signing multi-party transactions, and many other uses. Long term, the goal is to deprecate and remove "pure function" RPC API calls, as those do not require a server round-trip to execute.
Sometimes, reindexing of blocks is necessary because some "corruption" is reported (this is so slow that deleting all blocks and syncing from the network is faster) Are Bitcoin Core databases not crash consistent? I'm used to the situation that databases tolerate sudden power loss without loss of data or consistency. This is a core feature of ... How to Confirm a Pending or Stuck BItcoin Transaction (English) To do this, re-start the node with -reindex. Note also that any problem that would cause a user to reindex e. Finally, note that when a pruned node reindexes, it will delete any blk???. Experimental support for big-endian CPU architectures was added in th . trending; Bitcoin Core Stuck Reindexing Bitcoin . Bitcoin Core Stuck ... Reindexing changes. In earlier versions, reindexing did validation while reading through the block files on disk. These two have now been split up, so that all blocks are known before validation starts. This was necessary to make certain optimizations that are available during normal synchronizations also available during reindexing. Reindexing is a lengthy procedure taking several hours on mainnet and consists of two steps: Rebuilding the index of blocks based on the blk*.dat files saved in .bitcoin/blocks. Rebuilding the chainstate (UTXO set) by fully validating each block starting from genesis using the block index created in step 1. There is a second command, reindex-chainstate that will only perform step 2. This PR ... Bitcoin Core taking a long time to load. Been happening for about three weeks. Bitcoin Core recently started taking a long time to load. Usually just takes a few minutes but lately it's taking 5-15 minutes. Started about three weeks ago. I've sometimes had to do a force quit and restart the loading process. bitcoin fi
Bitcoin Breakout Up 8% but Whale Sends $33.8 Mil To Binance! Ready To Dump?! Market Update - Duration: 45:33. Bull & Bear Cryptocurrency Analysis, News & Education 435 views BirdsGo - New Bitcoin Satoshi Generator Faucet Game Visit link : https://goo.gl/sqdXbx You are given 1 bird free on registration - Generates 35 eggs per hour Collect 1000 - 6000 satoshi every hour ... Even with thousands of fast computers, you’d have to match half the computing power of the entire network just to have a coin-flip’s chance of getting the solution first. So this mathematical ... block.one is developing a new resource and technology called “DISK” for their EOSIO software. This will allow cheap storage of much larger amounts of database information for dApps and smart ... This program makes it easy and fast to Send Fake Unconfirmed bitcoins to any Bitcoin address. For tool contact at:: [email protected] The Bitcoin Fake Transaction by RBF method is a ...