-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Contract read & write #872
Conversation
Testing notes for @Liubov-crypto
|
@Liubov-crypto And I found a way to test the write actions. Can you create new Superhero wallet account and send me the seed? |
yes, from aestudio |
None of the contracts from aestudio cannot be verified or just some of them? |
I tried a couple but was not working for me |
Here I deployed some contracts: hamster AeForUsers AeUnlockOnTime scenario: Switch the wallet for the account to which you send me the seed Verify contract (ae studio examples + contract ids above) goto verified contract detail go to Write tab connect wallet, follow instructions execute write actions
|
Got issue with verification again: 2024-08-12.5.59.29.mov |
Finally I've managed to verify at least one contract from the list above: ct_JHVDvxUwSNiZDiMEqpjSF15gwPVvqRz2xXqf2vqw8aD76noSf but when I followed steps attached in video I got an issue: the page became grey and some issues in console, @janmichek could you check it please: 2024-08-13.6.11.12.mov |
@Liubov-crypto please retry now |
@janmichek There are some issues again: UnsupportedVersionError: Unsupported node version 7.1.0. Supported: >= 6.2.0 < 7.0.0, please check it 2024-08-15.4.12.18.mov |
Fixed. You can go ahead and continue with review. The test is not passing but i will solve it in parallel. @Liubov-crypto |
276da42
to
f4e7add
Compare
const connectedAddress = walletSdk ? Object.keys(walletSdk._accounts.current)[0] : null | ||
return !walletSdk || contractDetails.value.createdBy !== connectedAddress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const connectedAddress = walletSdk ? Object.keys(walletSdk._accounts.current)[0] : null | |
return !walletSdk || contractDetails.value.createdBy !== connectedAddress | |
return !walletSdk |
This is not an obvious restriction, contract should manage permissions by itself
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, fixed
Intereseting, I didn't find such a contract on testnet or mainnet. Could you send me the source code, please? I will verify it |
when I rechecked it on Read contract I got in read_test_value 5 as sum 2 and 3, and 33 in locally_add_two. are these numbers correct for the following fields? for me it looks like they switched. 2024-08-30.6.12.22.mov
2024-08-30.6.27.25.mov
|
Thanks for the review
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was not able to reproduce ad 3 today.
The rest is LGTM
Description
resolves #254
resolves #256
Demo
firefox_jVaQW0PNfH.mp4
Checklist: