Topic: [ANN][SLOTH] Slothcoin 1.3.1 build 3 AKA 300K fork - page 13. (Read 39486 times)

How long does it takes before a pending block comes available?
On http://wmikrut.com/tbs I only see pending blocks.
And when do I see the coins in my new wallet?
I quit mining because the miner crashes continously....

Great! Pool for version 1.3.1 build 3 workin' 
And we are 50-50 on the network!

Will the Pool get the 100 times a million starting block 300.000?

Sloth we go!

Working now again no need to remove the link

Will keep an eye on it.
If it takes too long I will remove the link.
(Probably needed to sync with the blockchain...  )

Pool not working at the momment... looks like it is off-line when i try to mine or at least the miner is trying to connect but nothing happens

(View image at MobyPicture)

Slothcoin to Proxima Centauri!

Get version 1.3.1 build 3 now!
www.slick.cf/coin/sloth/download

May the fork be with you!

Pool:
 
www.wmikrut.com (keccak / maxcoin)

So, there you have it, a fresh pool for Slothcoin version 1.3.1 build 3!

Make sure you start using version 1.3.1 build 3 in time!

Did you know that mining is the same until block 300.000?

• 125.000 SLOTH per block.

And with version 1.3.1 build 3, mining a million starts at block 300.000?

• 100 times 1.000.000 SLOTH per block

But only with version 1.3.1 build 3!
And mining goes on way into the year 2021.

May the fork be with you and use the Sloth for years to come!

You can use 1.3.1 build 3 just like 1.3.0, upto block 299.999.

Only starting block 300.000 1.3.1b3 will behave differently.
The reward system changes and the difficulty adjustment, that's all actually.

The blockvalue of height 295968 is chosen as a safety limit.
It is still a week before block 300K would kick in.
So if 1.3.1b3 is not used by a majority of peers, you could easily go back to using version 1.3.0 by then.

Have tried it, back and forth between version 1.3.0 and 1.3.1b3 and it works.
(Also exporting the wallet.dat then starting the old version 1.3.0 with it, confirmed to work.)

But this is considered only in worst case scenario, normally most peers would start using version 1.3.1 build 3 in time. 

This means that i can use 1.3.1 even if the network dont move to that version maybe?

No worries, the Slothcoin version 1.3.1 build 3 still uses the same blocksize.

Thx! Those Sloths are awesome. 

This looks like a good exciting coin work dev! Love sloths

slothcoinXT woot

What if there is no concensus on the Slothcoin network about moving to version 1.3.1 build 3 before block 300K kicks in? It needs to be considered that this might happen. Because only one 24/7 deamon updated and there are just a few other peers that seem to have done so until now. No worries yet, but from block 295968 it becomes crucial.

There are more coins up and about that exceed the 2^63-2 limit of the int64 variable of the MAXCOIN value. Some even consider to become POS, while they should go more towards POB (Proof Of Burn), I guess. And MAXCOIN is only there to limit the amount to be send to a maximum. Still it is an int64, signed, so only 63 bit really should be used, divided by 100.000.000, or the value of 1 COIN. But what are the chances of someone having 92 billion COIN, right? So the real COIN ever to be released will almost be like infinite...

If you do not understand this, never mind, back to the fork, or not the fork, that is the question.

Whatever the choice of the majority of peers within the Slothcoin network at block 295968, that version will be the one to continue. Be it version 1.3.0, than so it be. The community chooses. If three quarter of the connection agree to a certain version, then that should be it from block 295968 onwards.

Therefor it will be monitored closely if version 1.3.1 build 3 gets consensus or not by block 295968, if not it will be considered to be voted out. If that happens, the next is adviced, if you did run 1.3.1 build 3, like me, off course.

If by block 295968 Slothcoin version 1.3.1 build 3 has no 3/4 of the connections

• Stay Sloth, there is still about a week to go.
• (Always) Back up your wallet, preferable twice on two different media
• Stop the 1.3.1 build 3 version
• When needed, copy your wallet to the 1.3.0 user folder.
• If in seperate folders. Remove the old 1.3.0 'blocks' and 'chainstate' folders.
• If needed, copy the 1.3.1b3 'blocks' and 'chainstate' folders to the 1.3.0 user folder
• Start version 1.3.0 (Qt or deamon) again
• Be Sloth while it checks the blocks and wallet
• See what happens in the future, and keep the Sloth goin'

For me, this project is considered to be a learning proces. I like the way the community made an effort to make a difference to keep the Sloth going. And it will probably do so with version 1.3.0. Have no idea what will happen if the overdraw in Slothcoin goes beyond 2^63-2, time will tell. Somewhere around block 330K this will be the case. (In the sourcode MAXCOIN has no real impact, it seems, but only the limit on the amount one is able to send in one go.)

Currently we are still about 4 weeks away from that switchpoint. But when the fork gets no consensus in time then it will be needed for all peers to get back to version 1.3.0, to get the Slothcoin going. And for me the signal to leave and do something else, and put this fork on ice.

Just doing my best to stay realistic, as it might be the scenario that could happen.

Stay Sloth!

Somewhere it has been mentioned that there were only 2, 3 connections, tops.

Makes sure you have your settings right in your Slothcoin.conf, it should contain, amongst other stuff:
This is the part that 'says' listen to port 5107, which is default actually, but just to make sure.

If you use 'listen=0' then Slothcoin would pick a random available port. But the network seeks contact, so to speak, at port 5107, always, 'cause that is hardcoded. Meaning you could only 'find' peers that are hardcoded into the software, or added in Slothcoin.conf via addnode=...., currently that would mean 3 at the most.

For a decentralised peer to peer network to function properly, in this case TCP connected, a default port needs to be known and peers need to have it 'open' and / or forwarded in their router / modem. WinX (meaning all Windows type OS's) computers could use something like UPNP to fix this automaticly. But that would mean your modem / router supports that. And not a lot do, if I remember correctly.

This is a bit of a shortcoming of the way most xCoins make their connections over TCP. In practise this would mean you'd have to open / forward your 5107 TCP port manually. And, off course, give permission in your firewall.

Could this be made easier? Well when you look at software like StreamerP2P, you might think so, this works like a charm, but it uses UDP. And with Wallet software you always want to be sure your data was send and received. But this could be fixed with UDP to, by building in a control system. Why because UDP could be used for so called hole punching, no need to open ports manually, the software will do this with help of a superpeer.

But I've got a feeling that it is somewhere beyond the subject of an ANN thread.  

Anyway, to support the Slothcoin network, and also your own wallet and mining, open and / or forward port 5107 to the computer you have Slothcoin running on. If you have another port localy, just forward port 5107 to that one. That's what your router / modem is there for.

If you set listen=1 and port=5107 (or another routed local port) the network of Slothcoins can connect to you and vica versa. So Slothy a stronger bigger network will be build.

Always good to backup your wallet. 

Happy celebrations!

Hah, the Slothgod likes me, I did indeed take them off the exchange and stored them on some usb backups lol... I'll celebrate by dedicating a rig at this for a week

Hm, need to have a real good look at the network code part, amongst things to do...

But not now, have an awesome weekend!

And may the Sloth be with you!

They are all hardcoded.

And those are the ones everybody normally gets connected to the fastest.
But after that is seems nada di nada if you do not have the 5107 port opened / forwarded.

Well, actually it makes sence now.