Add way to view contract source in Wallet UI
See original GitHub issueWhat is the Problem Being Solved?
The source code of contract instances is available to be viewed on-chain (TODO: add link to API doc). It would be great if there was a convenient way to view the source through the wallet UI.
Description of the Design
Some possible considerations:
- Being able to click a
<>button on offers to view the source code of the contract - Being able to view the boardId of a contract, look up the contract code based on a boardId
- Being able to use sourcemaps somehow to view an un-minified version of the contract code?
Security Considerations
Test Plan
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How To Verify a Smart Contract on Etherscan | Chainlink Blog
Paste the contract's source code into the “Enter the Solidity Contract Code below” input box, solve the Captcha, and click the blue “Verify...
Read more >Integrate Your Smart Contract With a Frontend - Web3 University
In this tutorial, we will be working in this directory, as you learn how to bring this UI to life by connecting it...
Read more >How to Connect your Smart Contracts to Metamask - YouTube
We learn exactly how web3 / blockchain / smart contract applications work in the front end using HTML and Javascript.
Read more >Sequence, Ethereum Smart Wallet Contracts - GitHub
Install the Sequence Wallet libraries -- yarn add @0xsequence/wallet or npm install @0xsequence/wallet . To view the source, of the wallet libraries, see...
Read more >Integrating Your Smart Contract with the Frontend
In this tutorial, we will be working in this directory, as you learn how to bring this UI to life by connecting it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

cc @turadg
Any mechanism that discloses the code would cover the minimal requirement; e.g., it doesn’t need to be a code viewer. Providing the bundle zip file should be just fine. That would allow after-the-fact clients to extract code and show it, or dump it to a tree and open vscode on it. Just getting the hash would be fine if we had a reliable way to publish the source code that would verify the hash.