-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XDC21 standardization #796
base: dev-upgrade
Are you sure you want to change the base?
Conversation
* reduce mainnet timeout to 10s * reduce testnet to 10seconds --------- Co-authored-by: liam.lai <liam.lai@us>
Testnet merge back to mainnet
All fonts standardized for XDC21, the contract published on the main page has already been adjusted on constans.go. This update can be done without impact on the network, when we are all updated the XDC21 technology will be functionally available.
Monthly Merge from dev upgrade branch to master
Could you please rebase your commits onto our dev-upgrade branch ? Your dev-upgrade branch is based on our master branch now. |
It seems that this PR only modified the names of variables, functions, contracts. |
Yes, only this. |
And contract for XDC21 on mainnet, just tha address to this works. And the contract for XDC21 on mainnet, and the address for the technology to work. If published, I will make a website so we can deposit gas fees. |
Proposed changes
Changes aimed at starting support for XDC21 on the XDC mainnet. Changes have no impact on the network and nodes can be updated one by one. Routines for NIST standard SHA256 were created to validate transactions with this standard, tests are being carried out on the subnet.
Types of changes
What types of changes does your code introduce to XDC network?
Put an
✅
in the boxes that applyImpacted Components
Which part of the codebase this PR will touch base on,
Put an
✅
in the boxes that applyChecklist
Put an
✅
in the boxes once you have confirmed below actions (or provide reasons on not doing so) that