Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
I Fixed the Scalability Trilemma. Peer Review please.
ajaxprime
Member Posts: 1 ✭
Hello everyone,
I have a fix for the blockchain scaling problem. It allows for scaling up to billions of transactions per second.
The fix works like this :
The scaling issue starts at the coin base. If mining reward is issued according to consensus by a future miner based on a factor of the difficulty target, then effectively two chains are the same.
How do you prevent counterfeiting / double spend? Simply accept any chain as valid which mentions the sequence of the time stamp of the mother chain in the same order in its block headers to indicate the timeline of how the chain progressed.
Transfers can happen between different chain at same face value by an ecosystem of payment transferrors.
A simple image illustrating the fix: https://pasteboard.co/HD6ALBV.png
I will be publishing my paper shortly.
I have a fix for the blockchain scaling problem. It allows for scaling up to billions of transactions per second.
The fix works like this :
The scaling issue starts at the coin base. If mining reward is issued according to consensus by a future miner based on a factor of the difficulty target, then effectively two chains are the same.
How do you prevent counterfeiting / double spend? Simply accept any chain as valid which mentions the sequence of the time stamp of the mother chain in the same order in its block headers to indicate the timeline of how the chain progressed.
Transfers can happen between different chain at same face value by an ecosystem of payment transferrors.
A simple image illustrating the fix: https://pasteboard.co/HD6ALBV.png
I will be publishing my paper shortly.