Ecosystem & Operations
With Caduceus, developers can now effortlessly integrate Arcana Network’s Auth SDKs into their dApps, facilitating smooth user onboarding and offering instantaneous, secure in-app wallets.
Community Updates & Activities
The Caduceus Video Competition has been extended until July 15th. Grab your camera and create a video that best introduces what Caduceus is to the world. Share it on your social media channels, and we will select 5 lucky participants to share a total reward of 5400 $CMP.
Competition Link: https://taskon.xyz/campaign/detail/3979
Caduceus Technical Report
Block Explorer updates:
- Back-end: Fixed the issue where the opcode utility is unable to parse the 0x prefix
Testnet V2.0 (Pegasus) development:
MetaNet P2P Module:
- Addressed the issue of recurrent transmission of single-node multithreaded data
- Stress test: two nodes and two threads transmitted one terabyte of data continuously for eight hours
MetaRing Gateway Node:
- Added: Startup parameters are read from the configuration file by default
- Unit Tests: Commenced fatigue testing
MetaNebula VerificationNode — MetaNebula module:
- Finished integrating MetaVM (CaduVMs) submodules
- Resolved the problem with Gas estimation and contract inquiries
- Parallel transaction use case test: The balance was deducted, but the transaction failed (unresolved)
- Executed multiple irrelevant transactions, VM reports transaction conflict, re-execution error (unresolved)
- The transaction receipt for CRC721 transfer/CRC20 to the account is a failure (unresolved)
- Multi-layer calls: N Transferring funds from calls N A contracts (internal call B contracts) to account A amount miscalculation (unresolved)
MetaVM (CaduVMs) submodule:
- Problem-Solving: When multiple forms call multiple contracts and ultimately operate the same account, this problem is not limited to a particular form of transaction; as long as the transaction is sent in this manner, it will cause issues
- Problem-Solving: In the multi-transaction blended call, a specific transaction has a conflict and must be re-executed. The result of the transaction is normal, but the status of the received receipt is anomalous. The reason for this is because the retried transaction did not replace the consumed Gas
- Problem-Solving: Multiple transactions are combined and initiated, and conflicting transactions are identified and re-executed; however, there may be more than one conflicting key in a transaction, so the transaction may be repeated multiple times; therefore, the solution is a conflicting address. Once a conflict is detected, the transaction will be re-executed and conflict detection for the current transaction will cease
Join the community:
Caduceus Website: https://www.caduceus.foundation
Discord: https://discord.com/invite/caduceus
Twitter: https://twitter.com/Caduceus_CMP
Telegram: http://t.me/CaduceusMetaverse
Instagram: https://www.instagram.com/caduceus_cmp/
