You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introducing DaVinci Chain combines cutting-edge technology with sustainable practices to create a blockchain ecosystem that's both powerful and environmentally conscious with proof of stake
Thrilled to put DaVinci on Metamask.
Looking forward to your support, thank you.
Scenario
As a user, I want to easily connect my MetaMask wallet to the Davinci Chain network so that I can interact with decentralized applications (dApps) and manage DCOIN assets seamlessly without manually configuring network settings.
When the user clicks "Add Network" in MetaMask, the Davinci Chain should appear with its correct RPC URL, chain ID, currency symbol, and logo, ensuring a smooth and trustworthy user experience.
We follow the STRIDE threat modeling framework to assess potential risks:
Spoofing:
Chain ID uniqueness is enforced (28058), preventing network collision attacks.
RPC endpoints served over HTTPS to prevent MITM attacks.
Tampering:
RPC servers are secured with TLS.
Only validated smart contracts are recommended for users.
Repudiation:
Transaction history is recorded immutably on the blockchain.
All RPC requests are logged internally for auditing purposes.
Information Disclosure:
No sensitive data is exposed through the RPC endpoints.
MetaMask and WalletConnect connections are encrypted.
Denial of Service (DoS):
RPC servers are protected using rate limiting, load balancing, and firewall rules.
Elevation of Privilege:
No administrative overrides exist within the client connections.
Only user-signed transactions are processed, adhering to EIP standards.
Security Best Practices:
Full HTTPS encryption on all endpoints.
OpenRPC schema compliant.
Minimal metadata exposure to prevent fingerprinting.
Continuous security monitoring.
Reference Frameworks:
STRIDE Threat Modeling (Microsoft)
OWASP Blockchain Security Guidelines
EIP-1328 (Wallet security improvements)
Acceptance Criteria
Acceptance Criteria
Davinci Chain appears correctly when adding a new network via MetaMask.
RPC URL https://rpc.davinci.bz is reachable and returns valid JSON-RPC responses.
The native currency shows as DCOIN (Davinci Coin) with 18 decimals.
The chain ID is correctly set to 293 without conflicts with other networks.
The Davinci Chain logo is displayed properly in the MetaMask UI.
The explorer link (https://mainnet-explorer.davinci.bz) is clickable and opens the correct block explorer.
No warnings or errors are thrown when interacting with the network from MetaMask.
All metadata follows the EIP-3085 and EIP-3091 standards.
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
What is this about?
Add official network icon for DaVinci Chain.
Introducing DaVinci Chain combines cutting-edge technology with sustainable practices to create a blockchain ecosystem that's both powerful and environmentally conscious with proof of stake
DaVinci Mainnet
Chain ID: 293
RPC: https://rpc.davinci.bz
Explorers: https://mainnet-explorer.davinci.bz
Validator Explorer: https://validator-explorer.davinci.bz
Chainlist: https://chainlist.org/chain/293
Thrilled to put DaVinci on Metamask.
Looking forward to your support, thank you.
Scenario
As a user, I want to easily connect my MetaMask wallet to the Davinci Chain network so that I can interact with decentralized applications (dApps) and manage DCOIN assets seamlessly without manually configuring network settings.
When the user clicks "Add Network" in MetaMask, the Davinci Chain should appear with its correct RPC URL, chain ID, currency symbol, and logo, ensuring a smooth and trustworthy user experience.
Design
Official Network icon:
Technical Details
Technical Details (for technical tasks only)
Threat Modeling Framework
Threat Modeling Framework (for technical tasks only)
We follow the STRIDE threat modeling framework to assess potential risks:
Spoofing:
Tampering:
Repudiation:
Information Disclosure:
Denial of Service (DoS):
Elevation of Privilege:
Security Best Practices:
Reference Frameworks:
Acceptance Criteria
Acceptance Criteria
https://rpc.davinci.bz
is reachable and returns valid JSON-RPC responses.https://mainnet-explorer.davinci.bz
) is clickable and opens the correct block explorer.Stakeholder review needed before the work gets merged
References
The text was updated successfully, but these errors were encountered: