Web3 specifications #2247
Replies: 9 comments 16 replies
-
|
It's seem simple to develop a website that embed the compilation of a smart contract too. The compiler is already a package npm! 😄 https://www.npmjs.com/package/assemblyscript |
Beta Was this translation helpful? Give feedback.
-
|
is there documentation/examples on how to compile arbitrary stuff from assemblyscript in a browser using this package ? Sorry I'm not a big expert on the topic |
Beta Was this translation helpful? Give feedback.
-
|
Relevant links: |
Beta Was this translation helpful? Give feedback.
-
|
Also relevant: |
Beta Was this translation helpful? Give feedback.
-
|
There was a previous effort of design here massalabs/massa-sc-runtime#44 |
Beta Was this translation helpful? Give feedback.
-
|
Since the scope of that previous issue was well defined and it's not entirely related I created another discussion but we can merge the two issues. |
Beta Was this translation helpful? Give feedback.
-
|
Relevant link for compiling to wasm in the browser: |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
These guidelines explain how we should integrate the AssemblyScript SDK in browser! |
Beta Was this translation helpful? Give feedback.
-
|
@BatiGencho I was considering simply wrapping all current client endpoint this way: /* web3/private.js node administration relying on private Node API */
export const unban = ipAddrs => { /* TODO */ } // unban a given IP addresses
export const ban = ipAddrs => { /* TODO */ } // ban a given IP addresses
export const node_stop = () => { /* TODO */ } // stops the node
export const node_get_staking_addresses = () => { /* TODO */ } // show staking addresses
export const node_remove_staking_addresses = addresses => { /* TODO */ } // remove staking addresses
export const node_add_staking_private_keys = privateKeys => { /* TODO */ } // add staking private keys
/* web3/public.js node instrumentation relying on public Node API */
export const get_status = () => { /* TODO */ } // show the status of the node (reachable? number of peers connected, consensus, version, config parameter summary...)
export const get_addresses = addresses => { /* TODO */ } // get info about a list of addresses (balances, block creation, ...)
export const get_blocks = blockIds => { /* TODO */ } // show info about a block (content, finality ...)
export const get_endorsements = endorsementIds => { /* TODO */ } // show info about a list of endorsements (content, finality ...)
export const get_operations = operationIds => { /* TODO */ } // show info about a list of operations = (content, finality ...)
export const buy_rolls = (address, rollCount, fee) => { /* TODO */ } // buy rolls with wallet address
export const sell_rolls = (address, rollCount, fee) => { /* TODO */ } // sell rolls with wallet address
export const send_transaction = (senderAddress, receiverAddress, amount, fee) => { /* TODO */ } // send coins from a wallet address
export const send_smart_contract = (senderAddress, bytecode, maxGas, gasPrice, coins, fee) => { /* TODO */ } // create and send an operation containing byte code
export const read_only_smart_contract = (bytecode, maxGas, gasPrice, address) => { /* TODO */ } // execute byte code, address is optionnal. Nothing is really executed on chain
/* web3/wallet.js module that will under the hood interact with WebExtension, native client or interactively with user */
export const wallet_info = () => { /* TODO */ } // show wallet info (private keys, public keys, addresses, balances ...)
export const wallet_generate_private_key = () => { /* TODO */ } // generate a private key and add it into the wallet
export const wallet_add_private_keys = privateKeys => { /* TODO */ } // add a list of private keys to the wallet
export const wallet_remove_addresses = addresses => { /* TODO */ } // remove a list of addresses from the wallet
export const wallet_sign = (address, string) => { /* TODO */ } // sign provided string with given address (address must be in the wallet)
/* web3/main.js would help set up providers this way: */
const client = web3({
private: ["145.239.66.206:33034"],
public: ["145.239.66.206:33035"],
wallet: ["web-extension", "native-client", "user"] // sorted by decreasing precedence
}) |
Beta Was this translation helpful? Give feedback.
-
|
apis look good to me considering this is what we already support in Rust @yvan-sraka Regarding the client, I feel it needs to be a bit more type-safety oriented meaning we could either use constants such as ethersjs or web3js do or have an option for the user to define his own url. e.g. const Network { PRIVATE = "."145.239.66.206:33034", PUBLIC = "145.239.66.206:33035" } , then client.setCustom(new ConnectionUrl("")) and another class for the wallet where we could set attributes similarly to other js clients. |
Beta Was this translation helpful? Give feedback.
-
|
To keep track of work advancement in this discussion, everything have been implemented here https://github.com/massalabs/massa-web3/blob/main/web3/Client.ts 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
On a second thought the following commands should probably not be implemented as they rely on the knowledge of the private key: export const buy_rolls = (address, rollCount, fee) => { /* TODO */ } // buy rolls with wallet address
export const sell_rolls = (address, rollCount, fee) => { /* TODO */ } // sell rolls with wallet address
export const send_transaction = (senderAddress, receiverAddress, amount, fee) => { /* TODO */ } // send coins from a wallet address
export const send_smart_contract = (senderAddress, bytecode, maxGas, gasPrice, coins, fee) => { /* TODO */ } // create and send an operation containing byte codeThey should be replaced by the
|
Beta Was this translation helpful? Give feedback.
-
|
The wallet_generate_private_key command is more of a tool than something intrinsic. It could just be used to generate a private key, then we could call wallet_add_private_keys to add them. In the same logic, having the tools "derive_public_key(private key)", "derive_address(public key)" could be useful. From the standpoint of the wallet, having a "verify(message, signature, wallet_address) -> bool" to verify signatures is also useful |
Beta Was this translation helpful? Give feedback.
-
|
Something that will be reused a lot of time for each application is hashing and base58 encoding. It may make sense to add some utilities such as pubkey_from_private_key, address_from_pub_key, etc... |
Beta Was this translation helpful? Give feedback.
-
|
This is the current state of implementation of the web-extention wallet https://github.com/massalabs/massa-wallet/blob/main/massa/Wallet.js |
Beta Was this translation helpful? Give feedback.
-
|
This is now tracked here massalabs/massa-web3#13 |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
|
Maybe my goal could be to end up to have in every repo at least on |
Beta Was this translation helpful? Give feedback.
-
|
I think making demos is out of reach in the near future but could be fancy on the long term. I had Read The Doc in mind. I guess it's similar to docusaurus. Or mdBook. |
Beta Was this translation helpful? Give feedback.
-
|
My idea would be to do something similar to https://docs.soliditylang.org/en/v0.8.13/ (hence RTD). |
Beta Was this translation helpful? Give feedback.
-
Tooling
|
Beta Was this translation helpful? Give feedback.
-
|
@gregLibert we can also write a list of "Examples" thanks to |
Beta Was this translation helpful? Give feedback.
-
|
Including the Assemblyscript compiler in the SDK to be able to interact with smart-contracts from websites is a pain point. In the short term we have been discussing the possibility to add a remote endpoint that compile a given |
Beta Was this translation helpful? Give feedback.
-
|
I will document in massalabs/massa-web3#10 why in fact it's not much a paint point, and what working solution we already used in the PoC! But I'm glad of the creation of the |
Beta Was this translation helpful? Give feedback.
-
If I want to integrate smart contract interactions to a decentralized site web we have to compile different SCs to wasm each time a different user wants to perform an action. Right now it's not really convenient to do that as there is no easy way (AFAIK) to do that directly. It would be nice to improve the tooling so that people can develop dApps more easily.
I see two possible ways:
@z80dev what's your take on this ? Since you know well the ETH and Solana ecosystems it would be nice to have your feedback on what was nicely done there and what could have been improved.
cc @damip
Beta Was this translation helpful? Give feedback.
All reactions