Thanks again.
I think the issue is that I can’t receive without creating a receive request for the specific token, and I can’t do that due to a scratchpad fork error.
Also, right now the app isn’t connecting to the network… I’ll try again later!
Thanks again.
I think the issue is that I can’t receive without creating a receive request for the specific token, and I can’t do that due to a scratchpad fork error.
Also, right now the app isn’t connecting to the network… I’ll try again later!
Just checking in to ask whether there’s been any resolution for the scratchpad fork error so that receive requests are possible?
Also, can I please have some TT1?
Public key to receive TT1: b4f29a7f1d624fac8bdb76488153ef45db8bfe8e44b5e80222570c87dedf4ecaf4e6606ce3bae150eac0ca95998addf4
I managed to get a public key to receive GRUMP, so if you’re able, could you send some to me?
Here’s my public key for GRUMP:
9859e3e0fd847d0a86c9543d52eab02d11e49420d410998750b5074cf64772f041ca66373ecb3d1045086749bebc6a85
Let me know the spend address once it’s sent ![]()
Did you receive my FLAT ok?
Edit: info to receive your FLAT: acd5945760d40e294391a7b92b4a2db339bbbd356d65f9c237f885450e51c4c87a17ea3abdd8e69b860a5a1cea48c5e5
Ok will do ![]()
I’ll check for FLAT now.
Yeah I see the FLAT in my wallet TYVM
There is some GRUMPcoin for you at
b5d5cc79d6d0207c8806553104822d2d0848b6b19bc9c5d15e0d94154e0dde565e827b500b6a9bdc1f070270c96ae1f6
That’s great the FLAT arrived ![]()
Unfortunately it says ‘Could not find your Public Key in the spend’ when I try to receive the GRUMP.
Did you definitely pay it to the public key 9859e3e0fd847d0a86c9543d52eab02d11e49420d410998750b5074cf64772f041ca66373ecb3d1045086749bebc6a85 ?
Looks llike a copypaste fail there
Try this one
b0f003988a4731a382b8b2438d8844d464843ec1c1a2797d011a1c2ca8e980b841e2e7f5d5ccfbbbdc0c3454ca0f60ef
I have received the GRUMPs!
![]()
Thank you, and have a good weekend… now I’m off for pizza ![]()
Congratulations, guys! Thanks for your persistence
I’m working on merging the scratchpad fix, and user guide. Soon™.
I’ve added user instructions:
Ok, so I’ll answer here to not hijack the other thread.
For the genesis event could you not make the immutable address of the genesis event the identifier of the token. This if a transaction is for a token with identifier 0x, then only need to verify the genesis event by reading that one record at that address. IE the network itself validates the genesis event record
Bridged ERC20 tokens have multiple genesis events, so I think it’s not possible to verify only on Autonomi side, because a burn transaction on Arbitrum side has to be verified as well.
There are some changes to the token design proposed together with exchange scheme, perhaps this will make some things more clear:
Details of exchange process.
Just updated APIs from a new Autonomi release, scratchpad issues should be gone:

Autonomi Community Token Wallet App (alpha). Changelog: (chore) update autonomi to 0.6
Now to testing! ![]()
Distressing…
willie@gagarin:~/projects/maidsafe/community-token/act-wallet$ yarn tauri dev
yarn run v1.22.19
warning ../../../package.json: No license field
$ tauri dev
Running BeforeDevCommand (`yarn dev`)
warning ../../../package.json: No license field
$ vite
VITE v6.3.4 ready in 1018 ms
➜ Local: http://localhost:1420/
Running DevCommand (`cargo run --no-default-features --color always --`)
Info Watching /home/willie/projects/maidsafe/community-token/act-wallet/src-tauri for changes...
Downloaded ant-protocol v1.0.8
Downloaded ant-evm v0.1.17
Downloaded autonomi v0.6.0
Downloaded ant-bootstrap v0.2.7
Downloaded self_encryption v0.33.0
Downloaded 5 crates (493.3KiB) in 12.60s
Compiling ant-protocol v1.0.8
Compiling evmlib v0.4.3
Compiling ant-logging v0.2.52
Compiling self_encryption v0.33.0
Compiling act-wallet v0.0.5 (/home/willie/projects/maidsafe/community-token/act-wallet/src-tauri)
Compiling ant-evm v0.1.17
error[E0658]: `let` expressions in this position are unstable
--> /home/willie/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/ant-evm-0.1.17/src/data_payments.rs:99:20
|
99 | if let Ok(quote_peer_id) = quote.peer_id()
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
For more information about this error, try `rustc --explain E0658`.
error: could not compile `ant-evm` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error Command failed with exit code 101.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Been there, done that
Rust has to be updated to 1.88 or newer.
8640973b7a894dcb58a76f8bd3f67850e9dbdd8e5e70b748f1a7f2c9c6d65403b28109f9dbbda6b0ed04475504fec8a0
Have some GRUMP ![]()
8c720bb0fb2ffbf25156ba9cdcb52611bb4344fef5dbe322b16fa8bfcc6b19a00d3ab654397c2edf8ea4b7e5d1ef9183
I’m catching up after a long while away, but is the Community Token still going to be Digital Bearer Certificates? Sorry in advance if this has been answered already.
Unfortunately it seems not. Autonomi say it will put them in legal jeopardy, and they can’t deliver an anonymous token.
They say the implementation was working, so in theory the code is there and could be implemented, but there’s no plan to do so.
our bags are worthless as it is id vote lets go for gold and go with out own DBC variant FTW!!
Can we borrow any of Aleph Zero’s technical designs for tokens and smart contracts? Just throwing it out there as the their approach seems both similar and unique to Autonomi.