Great to see this @Anselme. I admire your coding ability and expect to learn a lot from this. I will be interested to see how it develops too.
Without having tried it (it’s cocktail hour here) I’ve noticed attacks on what I regard as important public datasets mounting, such as on the Internet Archive and just recently Wikipedia, from both corporations and government.
So my wish would be for individuals to use Autonomi apps to preserve these and similar datasets to ensure continued access.
Should those attacks succeed in hampering access or worse, it would also be a great example of why this network is so important.
# currently uses the bleeding edge of the autonomi API which will eventually be released but for avant-garde users here's a how to guide
# go back one directory out of the ant-upload directory
cd ..
# clone the autonomi repo and use the client-light-networking branch
git clone https://github.com/autonomi/autonomi.git
cd autonomi
git fetch origin client-light-networking
git checkout client-light-networking
# go back into the ant-upload directory
cd ../ant-upload
# build the release version of the app
cargo build --release
I’m compiling right now with the instructions above
except I changed git clone https://github.com/autonomi/autonomi.git
to git clone https://github.com/maidsafe/autonomi.git , renamed my autonomi folder to nautonomi and just followed the rest of the instructions - simples
I am getting this on Wallet error: ChunkPaymentsContract(RpcError(ErrorResp(ErrorPayload { code: -32000, message: "execution reverted"all uploads from home with all tools so its not your problem, its mine
Just tested on mainnet @Southside, although I didn’t get the same error it seems retrying did the trick in my case (cf ant.jpg).
I’ve notified the smart contract team about your error, I trust they will find a fix for you!
And my comment was not meant in a snarky way, even though I certainly understand that it can seem so. I was just wondering how others can spot the important differences between how it is vs. how it should be so easily? I guess that’s just experience and in general knowing what you are doing
Anyway, thanks for making this! GUI -stuff is certainly something I’ve been looking for.
I got this PDF years ago and the first couple of chapters are really just getting you to look at strings and the subtle differences between two lines that look absolutely identical but…
Lots of exercises and hard work for a few hours but well worth it.
And only after that he moves on to trying to teach you absolute basic Python.
I might still have it on an old HDD somewhere, but its no longer on this box.
Really useful exercises.
EDIT
Found it !!
Zed Shaw of Learn Python the Hard Way has an uncompromising style
Could it be that at the time of the transaction, the account 0xc753ba57e0f8ba81bacf73ac1b9242733d39a646 had a very low balance of ETH (like less than $2.50)?
I’m asking because the account needs enough ETH balance to pay for the worst case transaction fee scenario. By default the max fee per gas is set to 0.2 GWEI, which is a relatively high amount. The average Arbitrum One gas fees are about 0.015 GWEI. But there are often days where the fees are considerably higher than average, that’s why we set the default so relatively high.
So you should either add a small amount of ETH to the account or If you want to be able to pay for transactions on an account with a very low ETH balance, you can try playing around with the --max-fee-per-gas <WEI> parameter for the CLI or the Wallet.set_transaction_config method if you are using the autonomi sdk. You could set it to 15000000 WEI and go up from there to see what works for you.
We’re working on a feature that will automatically set the max fee per gas to the current market average to avoid having to tweak it manually.