It is now officially beer o’clock for you lot
WTF are you doing still hanging around???
GTF - go relax…
oh and thank you - all of you
It is now officially beer o’clock for you lot
WTF are you doing still hanging around???
GTF - go relax…
oh and thank you - all of you
Oh ok, so this should not happen or it’s a planned behaviour?
This one might collapse now folks, but I would just let it, we are gathering logs in any case, but right now I am switching off and after and chill. We have a lot of small tweaks and more simplifications again. Amazing stuff!!!
You should be able to connect to all Elders, so possible bug.
David… what part of beer o’clock are you not understanding???
Go relax NOW
Is it already possible to top up my cli balance somehow?
Why you think anybody cannot relax with a beer while farming chunks !
Im relaxing with a bridie beans and chips
THEN a beer, perhaps plural
I’m interested in this as well. I didn’t see a flag for “max size” in safe node --help
, safe node join --help
, or in the README
The “max size” for my node is 1.7GB which roughly matches the total free space available on the partition where I ran it. I wonder if, by default, it just queries the available free space, and sets that as its limit. Just guesswork though.
I was finally able to execute the safe node join command. I am waiting for the network to accept my node! Thank you for all your assistance today!
I managed putting the following, but I can’t cat it. Can anybody else?
sascha@Knut:~$ safe files put ~/Safe_Put/Safe_Nugget.png
FilesContainer created at: "safe://hyryyryhwrwpqnsqicrfqpetxdanbfu533zxw1ok5317psdwbrmfkqr6gjrnra"
+ /home/sascha/Safe_Put/Safe_Nugget.png safe://hygoyeympwmeijo94crkb134o68ugxajckgc1ir3147zk5tx5wt9d7y491a
I think you have it correct there - I am running two nodes, on laptop and desktop. One reports max size 142Gb the other 100Gb which is pretty close to the free space on both disks
oook !
I’m on the testnet on the pi4
I just needed to fiddle a bit with linking executables where they are expected, and then it works nicely.
My node has not joined yet, but I can now leave it running 24/24 on the pi.
You will be ready for testnet V4 so
Have a banana
Oi!!! @happybeing cheekybassa…
Your new vdash is giving me the finger…
and it calls itself an adult… Looks pretty childish to me…
Look who’s talking!
There are now many black holes and it is simpler to list connectable sections:
prefix:000,elders:01268306,06781385,0755ddd1,093a4907,1809bc34,1afa0a81,1dbaef19
prefix:001,elders:28440498,29b182ee,2c1d4bb2,2e205ed2,2f9253cf,30315679,3c01e3b4
prefix:01 ,elders:415f9981,437df2aa,4c9fb817,5281e8a6,533cabb7,7359bf43,751c2c38
prefix:111,elders:02184c7a,0b2aac32,52e4f56a,a88a01eb,abbef64f,cb32a429,e15332db
@stout77 node (2c1d4b…) and mine (012683…) are still running as elders, but I will kill mine soon.
Note that known elders in section 111 are mostly not right (only the last one belongs to said section). This is a problem I already mentioned as soon as testnet T1.
And @dirvine said as much a few hours ago. Basically if you can have fun with T3 before it implodes, go ahead but the devs have learned all they are going to from it now. They are taking a well-earned break and will be back fresh next week.
I’m tipping T4 on Wednesday morning, T5 - with only minor tweaks by next Friday. T5 will stay up for a couple of weeks for soak testing, I think.