Pages:
Author

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 19. (Read 284948 times)

hero member
Activity: 938
Merit: 1000
can anyone help with a conf file & nodes?
thanks

Afaik you don't need the nodes at all because it's hardcoded in the new client.
But if you insist:

Code:
debug=0
server=1
daemon=1
rpcallowip=127.0.0.1
rpcallowip=192.168.0.*
rpcallowip=localhost
rpcport=41684

# RPC information
rpcuser=user
rpcpassword=pass

Just a musing on the current implementation of Slimcoin.

Based on the burn decay rate of 0.001427 / day, as we approach 1.6 million coins burnt, the rewards tends to zero as the decay rate equals reward rate. The only reward would be from fees.

At such a burn decay rate, 2342 coins will decay, which would equal the PoW generation rate if the difficulty is 10 (3.5 SLM block reward * 720 / day), which is roughly 1Ghs, thus achieving kind of an equilibrium.

It provides quite an interesting dynamic circulation ceiling which tends to 1.6 million SLMs with heavy usage, yet increases gradually to 250 million with low volume.

Quite informative, thanks a123.
hero member
Activity: 655
Merit: 500
can anyone help with a conf file & nodes?
thanks
member
Activity: 98
Merit: 10
Just a musing on the current implementation of Slimcoin.

Based on the burn decay rate of 0.001427 / day, as we approach 1.6 million coins burnt, the rewards tends to zero as the decay rate equals reward rate. The only reward would be from fees.

At such a burn decay rate, 2342 coins will decay, which would equal the PoW generation rate if the difficulty is 10 (3.5 SLM block reward * 720 / day), which is roughly 1Ghs, thus achieving kind of an equilibrium.

It provides quite an interesting dynamic circulation ceiling which tends to 1.6 million SLMs with heavy usage, yet increases gradually to 250 million with low volume.
member
Activity: 98
Merit: 10
So there is still the PoW cost but how do the PoB blocks then contribute to the consensus?

How would an attacker with 51% of the PoW fair against defenders with various levels of burned stake?

I'm not too clear, but I don't think PoB can help defend against PoW 51% attacks. PoB does increase trust score of a chain for resolving forks but might not kick in in time for double-spend attacks?
member
Activity: 60
Merit: 10
So there is still the PoW cost but how do the PoB blocks then contribute to the consensus?

How would an attacker with 51% of the PoW fair against defenders with various levels of burned stake?
member
Activity: 98
Merit: 10
How does slimcoin deal with the "nothing at stake" problem? is it applicable?

I can see in the event of a PoW fork it would cost next to nothing to mine PoB on both chains and if you dont then you run the risk that you pick the wrong chain and lose the opportunity to have rewards for the time that consensus is being determined. Is this correct, if so what can be done to incentivize PoB minters to pick one chain?

As far as I understand, nothing at stake is a phenomenon that applies to pure PoS altcoins. PoB always depend on a preceding PoW which has a cost to mine (aka something-at-stake), so you can't chain PoBs consecutively to perform the N@S attacks.
member
Activity: 60
Merit: 10
How does slimcoin deal with the "nothing at stake" problem? is it applicable?

I can see in the event of a PoW fork it would cost next to nothing to mine PoB on both chains and if you dont then you run the risk that you pick the wrong chain and lose the opportunity to have rewards for the time that consensus is being determined. Is this correct, if so what can be done to incentivize PoB minters to pick one chain?
member
Activity: 98
Merit: 10
Mr T, eh? I like that.

Oops  Shocked

Yeap PMed you re the Amazon EC2 build environment!
newbie
Activity: 21
Merit: 0
Awesome! I'm testing it out right now, am spamming myself with 0.01 SLMs in hope of catching a PoB block. I'll PM you on regarding the Amazon EC2 build environment I compiled the Slim-Qt on Smiley

Ok fix confirmed, thanks Mr E! Will update the binaries soon Smiley
Yay, it worked. Smiley

I still have an OCD compulsion to go back in and tidy it up to use a function on the transaction class, instead of a boolean flag passed to the transaction-parsing function.  I might try doing that once I have the build environment set up...


P.S.
Updated https://github.com/kryptoslab/slimcoin/releases/tag/v0.3.2.1

Changes:

From hankrules: Added 2 dnsseed servers
From Mr T:       Fixed display bug for transactions in PoB blocks
From a123:       Fixed versioning, disabled sync checkpoint errors, added new RPC command "getsubsidy" to find out current PoW (for pool use)

(pi's version is still compiling...)
Mr T, eh? I like that.
legendary
Activity: 2646
Merit: 1722
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
Updated https://github.com/kryptoslab/slimcoin/releases/tag/v0.3.2.1

Changes:

From hankrules: Added 2 dnsseed servers
From Mr T:       Fixed display bug for transactions in PoB blocks
From a123:       Fixed versioning, disabled sync checkpoint errors, added new RPC command "getsubsidy" to find out current PoW (for pool use)

(pi's version is still compiling...)

Coolio. Update my nodes without a hitch. Good progress.

~ Raspberry of approval from our mascot

legendary
Activity: 2646
Merit: 1722
https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF
What time GPU miners coming Huh Huh

Hmm I was quite hoping it is truly resistant to GPU mining, similar to how Cryptonite has almost very little advantage over CPUs (assumption based on http://cpucoinlist.com/). Anyone has any insights on how Dcrypt holds up? Being a CPU-only coin has a certain appeal, and it might not be too late to switch to another algo in time for the fork.


Not insight, but from the whitepaper:

Quote from: Slimcoin Whitepaper
The Dcrypt algorithm is a “front-end” to the SHA256 hashing algorithm. Its main purpose is to prevent an ASIC dominated
proof-of-work mining scheme from occurring in Slimcoin. Allowing Slimcoin to become ASIC minable will overshadow
the proof-of-burn and proof-of-stake aspects of the coin. Dcrypt is made to be difficult to parallelize, require significant
amounts of memory, require significant amounts of reading/writing to/from memory. Also, the amount of memory required
is not a predetermined size. The hashing algorithm loops until a specific condition is met and for each loop, the size
increases.
It goes into more detail that quickly becomes beyond my comprehension Smiley  http://www.slimcoin.club/whitepaper.pdf

Indeed. Slimcoin is certainly not just a 'copy and paste' coin and has many innovative features.

Its quite remarkable that Slimcoin has had a relatively limited following up until now and that it was almost left to just crash and burn. (pun intended)
hero member
Activity: 798
Merit: 500
Difficulty is rising, it's back at what it used to be when the pools were active.

Are there any pools now? If this difficulty is done without ANY pool then it's insane!

"difficulty" : 0.20134940,

PS: I have a large amount of burn coins as well, over 2% of the total amount, but that is because i never stopped mining and when the diff was low i got many Smiley

"Net Burnt Coins" : 8074.81369400,
"Effective Burnt Coins" : 7389.20701100,
"Immature Burnt Coins" : 111.67010000,
"Decayed Burnt Coins" : 523.93658300
member
Activity: 98
Merit: 10
Updated https://github.com/kryptoslab/slimcoin/releases/tag/v0.3.2.1

Changes:

From hankrules: Added 2 dnsseed servers
From Mr T:       Fixed display bug for transactions in PoB blocks
From a123:       Fixed versioning, disabled sync checkpoint errors, added new RPC command "getsubsidy" to find out current PoW (for pool use)

(pi's version is still compiling...)
hero member
Activity: 673
Merit: 500
What time GPU miners coming Huh Huh

Hmm I was quite hoping it is truly resistant to GPU mining, similar to how Cryptonite has almost very little advantage over CPUs (assumption based on http://cpucoinlist.com/). Anyone has any insights on how Dcrypt holds up? Being a CPU-only coin has a certain appeal, and it might not be too late to switch to another algo in time for the fork.


Not insight, but from the whitepaper:

Quote from: Slimcoin Whitepaper
The Dcrypt algorithm is a “front-end” to the SHA256 hashing algorithm. Its main purpose is to prevent an ASIC dominated
proof-of-work mining scheme from occurring in Slimcoin. Allowing Slimcoin to become ASIC minable will overshadow
the proof-of-burn and proof-of-stake aspects of the coin. Dcrypt is made to be difficult to parallelize, require significant
amounts of memory, require significant amounts of reading/writing to/from memory. Also, the amount of memory required
is not a predetermined size. The hashing algorithm loops until a specific condition is met and for each loop, the size
increases.
It goes into more detail that quickly becomes beyond my comprehension Smiley  http://www.slimcoin.club/whitepaper.pdf
member
Activity: 98
Merit: 10
Awesome! I'm testing it out right now, am spamming myself with 0.01 SLMs in hope of catching a PoB block. I'll PM you on regarding the Amazon EC2 build environment I compiled the Slim-Qt on Smiley

Ok fix confirmed, thanks Mr E! Will update the binaries soon Smiley
member
Activity: 98
Merit: 10
What time GPU miners coming Huh Huh

Hmm I was quite hoping it is truly resistant to GPU mining, similar to how Cryptonite has almost very little advantage over CPUs (assumption based on http://cpucoinlist.com/). Anyone has any insights on how Dcrypt holds up? Being a CPU-only coin has a certain appeal, and it might not be too late to switch to another algo in time for the fork.

I believe I've managed to chase down the bug causing transactions to show up as "Mint by burn" when they actually weren't.

The code that did up the transaction list checked whether the transaction was in a PoB block, but forgot to check whether it was the coinbase transaction, with the result that all transactions in PoB blocks would show up as "Mint by burn". I'm not quite sure why the incorrect amount appeared in the list -- but try my patch and see if it fixes the GUI bug. (Or if you don't have a gui environment to test it on, I can do it if you compile an updated windows client. Haven't got a build environment of my own yet...)

(BTW, it looks like even the check for PoB block is kind of hacky -- the check for PoS blocks calls a wtx.IsCoinStake() function, but the check for PoB is implemented as a boolean flag passed in to the function by the caller... kind of ugly...)

Awesome! I'm testing it out right now, am spamming myself with 0.01 SLMs in hope of catching a PoB block. I'll PM you on regarding the Amazon EC2 build environment I compiled the Slim-Qt on Smiley
newbie
Activity: 33
Merit: 0
What time GPU miners coming Huh Huh
newbie
Activity: 21
Merit: 0
I believe I've managed to chase down the bug causing transactions to show up as "Mint by burn" when they actually weren't.

The code that did up the transaction list checked whether the transaction was in a PoB block, but forgot to check whether it was the coinbase transaction, with the result that all transactions in PoB blocks would show up as "Mint by burn". I'm not quite sure why the incorrect amount appeared in the list -- but try my patch and see if it fixes the GUI bug. (Or if you don't have a gui environment to test it on, I can do it if you compile an updated windows client. Haven't got a build environment of my own yet...)

(BTW, it looks like even the check for PoB block is kind of hacky -- the check for PoS blocks calls a wtx.IsCoinStake() function, but the check for PoB is implemented as a boolean flag passed in to the function by the caller... kind of ugly...)
member
Activity: 98
Merit: 10
I sent him 300SLMs for his explorer work and if you could send him some for the bounty he will be happy about this. SLM is one of hidden gems in cryptoworld now. Let's us accumulating alot more before it explodes Cheesy

I've received 5530 SLMs for donations and bounties to give away so far, think I'll organise a way to let donors vote where the SLMs go.

I've coded up a simple calculator while we wait for better ones, it's available in the Brain Wallet section of my slimcoin.club website, under "Burning SLM". A 50000 SLM burn currently gives an estimate of "482.056151 SLMS GENERATED PER DAY, 71.35 SLMS DECAYED.".
hero member
Activity: 938
Merit: 1000
just tried the linux version and it's complaining that the checkpoint is to old,but it's the actual block

Actually I have this issue too. Will fix this up in the next release! Created an issue on the tracker.

50k SLM burnt? LOL quite a number of burning money. Wink
I will ask my friend dcct about the ROI calculator for PoB.

Your friend is doing a lot Smiley

Yea I dumped most of my SLMs at it. Difficulty is getting high for dcrypt mining and I'm all in on SLMs - a good and verifiable show of confidence Cheesy

I sent him 300SLMs for his explorer work and if you could send him some for the bounty he will be happy about this. SLM is one of hidden gems in cryptoworld now. Let's us accumulating alot more before it explodes Cheesy
Pages:
Jump to: