Which command to do that?
safe wallet address
Thank you!
aa597b8ba613c2cd88b9511becdc11fd023d620eda79182bc91b080d1218762ff6264df58ba0b3d88cfc6f8ef712bcff
safe wallet receive 89cca6cccacc95cc9bcc54d1ccf2cc86cc4b06f9ccbfcc3a16e5ccc5cc7dfbccc9cc9acc98cce7cc70c4cc4badcc4119022d3ae0ccbacc1a03cccc6912264e0ec1ccb0cc423bc6cc15efcccecc0253704e7417f5cc046a7848d2ccd4cce2cc7abacc0dc2cc1d4b87cc8bccbbccdfcc077f1b6de0ccbccc1a3d82cc3a9ccc4ea4cc7ceecccdcc797054f6cceeccb9cc6000dcd6cc82cc7cd1cc6c3c4bbecc73628fccb7cc60becc234ed0cc73a0cc2865b8cc3ffccc44cecc3d106e27deccf4cc7a11d5cc57a7cc4a1c0febcc4c7522adccbecc72190571ffcc2dd1cc95ccc9cc2d06d0cc8ecce7cc581a09a6cc7a6d36b7cc063613798bcc250d9acc84cc83cc0e3585cc2329bbccf7cc4ca6ccdacca0cc31547d6888ccaccc18b0ccbdccf0cc757a9bcc8eccbdcc4f2c456b00dcb8cc7c739ecc8dcc56d4cc5a5680cc4a69e0cc8ecccfccd5cc8fcc9ecc98cc22a8ccb0cc3485cc4a1034cdcce7cc1f3a592ea1cc5a3027370ac1ccd6cc12aacc67abcccdcc99cc8ecc3000dc9391646574707972636e45a981
Thereās 30 for you!
here is some more
safe wallet receive 1fb2cc0ff8ccb4cc8fcc8bcc95ccffcca2cc3d252c46ebcc8fcce4cc2effcc748ccc721b1beacc0facccfcccb9cc7b15fdcc88ccb8cce1ccf4cc6c35b3cc215a1417e4cc15b9cc4309dfccd0cc177a8dcc12784ff7cc414a05accc0495ccb8cc18dacc43dccc81cce9cc5380cc4fe8ccc8cc7879afccd7ccb9ccadcce1cca5cc753d75e7cc6ce6ccf5cc80cc002db9cc9dcc89cc6000dc90cc32038fcca8cccecc39f4cc53becc96cc00400bfccc302873cccc64f7cc82cc595c99ccefcc9bcce4cc31afcc2a26677ef2cc6efeccc6cc0e025e0c144182cc2be8cc659acce7cceccc12a1cc1a032f05308bccdccc6a2852794e365a29c4ccd0cca0cc95cc6f30fccce8cc8ecc652b9eccc7cc282ae8cc1ae8cc531dd9cc00fbcc5b00dc6162d9ccacccd4cc28e0cc5a98cc99cc622488cc9acc80ccd1cc30494cd7cc80cc6aa4cc97cc72facc3a6493cca4cc559bccf7cc71fdccc0ccb1cc3661495e369dccb3cc18155eb9cc3000dc9391646574707972636e45a981
Thank you!
Thanks guys
Sent you 1200000000000000000 NanoTokens - happy uploading or transferring .
safe wallet receive 5e91cc538fcc82cc5d3426cfcc5873b2ccccccd3cc0188ccafcc97cc063f6259bcccd3ccc5cc1b08edcc9bcc75aacc5e26fbcc35116a07a0cc793312feccbccc080b29103943bacc5a594ceecc3eb2cc0eb8cc86cc2948c7cc72385b43d6cc17c2ccf2cc89cc660e150d2269ffccc9cccdcc08f5cc63b8cc7092ccd5ccbecc02e7ccb6cc33abccbaccb9cc6000dc8fcc19d2cc17c2cce3cc4eebcc3a87cc7d2c54033894ccedcc5c39e0cc95cce4cc70b9ccdbcc7bdbcc121b5adccc733dd0cca3ccb5ccc7ccfecc90cc5de8ccb7cc2c6ebccc120bf5cc32dacc156287cc735352e8ccd2cc51c9ccbccca2cc548ecc84ccf7cc5af4ccb1ccc1cc8dccb7cc488ccc4ff3cc7ab8cc151a0f2a102623c5ccc3cc85cc89cc48013ac2cc9cccd5cc8dcc8fcc0d14f6cc6400dc18415539b6ccbacc84cce9ccccccb8ccfacc91cc48b4ccf4cc37f2cceaccaecc50b7ccb4cc5b22f5cc4d0582cc20a6ccc8cc8ccc578bcc7a5184cc9acc6f3728f0ccc6cc7eaeccb6cc2aa5cc3000dc9391646574707972636e45a981
cc @roland whatās the correct setup here atm?
A new faucet could be started and funded by anyone with some $$. Although the current one gets all the money from genesis as things stand.
Thatāll change soon.
Yeh it will be attempting to double spend now.
Can you see the commit hash in your logs of the faucet build?
(If itās still happening weāll need a test to check this i think @anselme)
cc @Anselme good exercise to see if anything is slipping through the cracks here.
I believe a PR thatās gone in over the last days would have prevented this startup. before that we werenāt checking if a DBC had been spent before we credited it to our wallet (whatever wallet, the faucet should now bug out with this).
All good. Great to be poking at this and seeing what you;re up to
Not sure if this question was raised towards me? If so, not sure where to look now after having run the cargo build command a while back. The faucetās version shows up as:
sn_faucet 0.3.67
Overall, very exciting to see the network inch closer to the finish line (core components)!
Great work team!
Based on the testing over the weekend, below were some additional points off concerns (summary):
- If the wallet gets corrupted (or has these unconfirmed transactions state), its preventing uploads and transferring of coins, and if the solution is to wipe out the wallet folder, well that will likely not fly with the consumer who just lost his or her balance (assuming the priv key gets removed too), lol.
- Application panic in
safe
client when a file address is provided as an input for a folder download - There have been a few occasions where the network has uploaded chunks that didnāt exist on the network, but charged 0 payments for it (see some of my earlier comments below):
Maybe some of these are already in-flight or have been fixed since the snapshot off ValentinesNet testnet.
It was! thanks
It could be rebuilt. Itās just nuclear cleanup at the mo while the wallet is fleshed out and we move away from (implicit) chocolate coins to something⦠meatier?
@Jason_Paul this might be another one for you to dive into next.
@anselme Iām not sure if you know off the top of your head what might be going on here?
I see. Is that just dependent on keeping a copy of main_pubkey
and main_secret_key
in a backup location and copying those files back to the default paths such as ~/.local/share/safe/client/wallet
, in which case the safe
client will re-use those again?
Just curious, what does the wallet
file by itself hold on the location above? Is that the file that needs to be blown away at the moment to reset the state etc?
Yup. @mav is rightly keen for us to get to a tight / more secure wallet process and I think that will aid here a lot. Weād work on folk having to backup wallet seed phrases eg. That would probably be the first step. Then we automate the wallet rebuild/recovery so such nuclear issues are no longer necessary, eg.
Itāll come, and is hopefully not too far away!
is this longest testnet?
Ah, actually @shu the protective PR is not yet in as weāve failing tests there just now. So youād still be seeing this with latest faucet.
I have two machines at 100% on there hard drives and the rest are between 95% and 98%
I guess this is the end. There is excessive traffic probably due to full nodes being unable to replicate correctly and I donāt want to provoke my ISP too much, I have already 25 TB of traffic on this testnet. I am pulling the plug.
Iām not sure itās the final end! Yes, I can see traffic is way up over the last couple of hours. However, downloads are still working and so are uploads albeit more slowly. The point is they arenāt totally failing. Could it be that some nodes have left but some others have joined as well?
In the past weāve seen testnets go into a death spiral a lot more rapidly than this when lots of nodes have been removed. We might yet weather this storm as well. Donāt forget the removal of the hard limit of 2048 records so there is extra firepower of many nodes having more disk space. In the past all nodes have got to 2048 at roughly the same time and that has jammed it up suddenly.
I think the network is bigger as well this time.
12 hour graphs from AWS Instance with 1 node:-
@Shu sterling work with double spending! @anselme has dug in, replicated and found the issue (a TODO
thatās been neglected).
Seems like the core issue is related to nodes trusting incoming replicated spends blindly instead of validating them. There is a potential fix here , though weāll be working up some repro tests for CI to verify this and prevent regressions there.
Thanks for diving in and trying things! Itās all helpful!