Focuses on communications between enterprise-tier servers rather than the “P2P” interactions people often refer to. To do this, nChain developers have “gone back to the beginning,” identifying blockchain users and their needs. This included big data paradigms and horizontal scaling.
The original version of the Bitcoin node client had the facility to conduct IP to IP payments where a receiver could give a payer their IP address. New payment processes are in development and will allow network peers to interact securely using cryptographically verified IP addresses.
This limit will still exist as a configuration option for miners however the default will be changed to no limit at all. After Genesis it will be a miners responsibility to manage this limit if they choose to impose it at all.
Current Bitcoin Node accept non-standard TX in Block, it just reject non-standard TX received from p2p network. So it's campatible with existing consensus, new Node pack non-standard TX in block, old Node don't. But they both accept non-standard TX in block.
Our next roadmap article will describe the upcoming changes to OP_RETURN because this is a change we want the Bitcoin ecosystem to be aware of as far in advance as possible. The mechanism of that change is what this post is about and the reason we explain it separately is because it is a concept we will be reusing in many ways.
Bitcoin SV Proposals That Have Been Either Rejected or Abandoned
Add New Proposal / Development
Update Proposal / Development
Add Development Team
Through site feedback, content submissions, and donations, you help Coin Dance realize its vision. Your donations directly support site development, content quality control, and technical research, which is necessary for the project to achieve its goals of empowering the community and growing the ecosystem!