[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 51.

chiguireitor

legendary

Activity: 872

Merit: 1010

Coins, Games & Miners

Quote from: slimcoin on July 08, 2014, 04:54:35 PM

New update with getrawtransaction is up on github, there are no binaries for this update.

Other added commands include: getpeerinfo and listburnminted (lists the blocks minted by PoB by your client)

The update also makes the client start up significantly faster, but that requires you to delete the blkindex.dat and blk0001.dat files. If you do not delete them, the client will error out saying the blkindex.dat is corrupted.

Here is a link to the github slimcoin: https://github.com/slimcoin/slimcoin

Hmmm... sendrawtransaction wasn't included? also there's a need for signrawtransaction... plz plz pretty plz

slimcoin

full member

Activity: 182

Merit: 100

New update with getrawtransaction is up on github, there are no binaries for this update.

Other added commands include: getpeerinfo and listburnminted (lists the blocks minted by PoB by your client)

The update also makes the client start up significantly faster, but that requires you to delete the blkindex.dat and blk0001.dat files. If you do not delete them, the client will error out saying the blkindex.dat is corrupted.

Here is a link to the github slimcoin: https://github.com/slimcoin/slimcoin

sp00lin9

hero member

Activity: 490

Merit: 500

Quote from: slimcoin on July 08, 2014, 02:20:21 PM

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

Thank you!

chiguireitor

legendary

Activity: 872

Merit: 1010

Coins, Games & Miners

Quote from: slimcoin on July 08, 2014, 02:20:21 PM

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

Yay!!!! Will compile it tonite and add support to my IAPs system!!!

slimcoin

full member

Activity: 182

Merit: 100

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: glop on July 08, 2014, 10:39:32 AM

Slimcoin,

Have you any idea about the time it takes to turn the one loop in

Cwallet::CreateCoinStake

( because it is run by any coins in the wallet until fKernelFound and if you have many coins it could have a significant impact )

Dev has no internets at home, we will have to wait for an answer until tomorrow

glop

full member

Activity: 126

Merit: 100

   Slimcoin,

   Have you any idea about the time/ressource it takes to turn one loop in

   Cwallet::CreateCoinStake

  ( because when POS is active, it is run by almost any coins in the wallet until fKernelFound and if you have many coins it could have a significant impact )

glop

full member

Activity: 126

Merit: 100

Quote from: slimcoin on July 08, 2014, 07:40:02 AM

Yes, that is it.
But in that process, when does that happen?

Does it only happen when the coins are old enough, which is after the 1 week wait time, or when the coins can create a valid PoS block.

I had a look into the code:

The process is launch every block but the calculation and split is done after 1 week of coin age.

The perf problem should be into the election test as it tests every coins, it multiply the delay and load.

Now it is to find out were and why because it has to be really quick .......

chiguireitor

legendary

Activity: 872

Merit: 1010

Coins, Games & Miners

Clarifying some things:

The CPU utilization spikes come from the fact that the Staking needs to sign the individual transactions it is using. So, for example, you have around 200 incoming transactions from a pool, and you stake coins from 150 transactions, that means the wallet needs to sign EACH of the 150 transactions twice, one for the new staked part and one for the change part. ECDSA signing is particularly hard on the CPU because of the math involved and the HUGE numbers it uses.

If you send one transaction to another wallet containing all the outputs from the 200 transactions, you're simplifying the spendables from 200 to 1, making it easier to stake because now your wallet only needs to sign twice, not 300 times. That's why primer- solved it by sending all the coins to another wallet.

Alas, i haven't experienced this problem because i burn it all.

primer-

legendary

Activity: 1092

Merit: 1000

When this is done grab a pen and paper and do some math! Difficulty/reward estimation/prediction!

Both for PoW and PoB! Its BROKEN as it is. Add x10 current difficulty and rewards are almost non existant!!

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: glop on July 08, 2014, 09:10:17 AM

I think the CPU load is dependent of the quantity of transaction into the wallet whatever it comes (POS POB or POW) and it is generated by the POS process.

Lets leave PoS at 1 year - 1% (or 10% if you insist), as it was before block 15100. Problem solved!

DO IT NOW DEVELOPER OR THIS SHIT COIN IS GOING NOWHERE!!

glop

full member

Activity: 126

Merit: 100

Quote from: primer- on July 08, 2014, 09:05:07 AM

Quote from: glop on July 08, 2014, 09:01:51 AM

Quote from: primer- on July 08, 2014, 08:56:48 AM

Quote from: glop on July 08, 2014, 08:55:13 AM

Quote from: primer- on July 08, 2014, 08:53:39 AM

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

It does not fix the problem of quantity of transaction into wallets..... I mean dust coins

CPU itilization problem is triggered when there are hundreds of small PoS transactions. That wont happen if you increase PoS diff.

I think it is not only small POS transaction but also POW dust received from pools. I have that kind of dust into my wallet, I am sure you have as well (may be bigger dust Wink

).

My pool dust is not causing any cpu spikes whatsoever. I only had spikes when my wallet was minting PoS blocks. The second i encrypted the wallet cpu spikes dissapeared. I fixed the problem by moving all coins to a new wallet.

I think the CPU load is dependent of the quantity of transaction into the wallet whatever it comes (POS POB or POW) and it is generated by the POS process.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: glop on July 08, 2014, 09:01:51 AM

Quote from: primer- on July 08, 2014, 08:56:48 AM

Quote from: glop on July 08, 2014, 08:55:13 AM

Quote from: primer- on July 08, 2014, 08:53:39 AM

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

It does not fix the problem of quantity of transaction into wallets..... I mean dust coins

CPU itilization problem is triggered when there are hundreds of small PoS transactions. That wont happen if you increase PoS diff.

I think it is not only small POS transaction but also POW dust received from pools. I have that kind of dust into my wallet, I am sure you have as well (may be bigger dust Wink

).

My pool dust is not causing any cpu spikes whatsoever. I only had spikes when my wallet was minting PoS blocks. The second i encrypted the wallet cpu spikes dissapeared. I fixed the problem by moving all coins to a new wallet.

glop

full member

Activity: 126

Merit: 100

Quote from: primer- on July 08, 2014, 08:56:48 AM

Quote from: glop on July 08, 2014, 08:55:13 AM

Quote from: primer- on July 08, 2014, 08:53:39 AM

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

It does not fix the problem of quantity of transaction into wallets..... I mean dust coins

CPU itilization problem is triggered when there are hundreds of small PoS transactions. That wont happen if you increase PoS diff.

I think it is not only small POS transaction but also POW dust received from pools. I have that kind of dust into my wallet, I am sure you have as well (may be bigger dust Wink

).

IE: my wallet actually uses CPU and I have no coins into except burned coin and lot of POW dust from pool.........

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: glop on July 08, 2014, 08:55:13 AM

Quote from: primer- on July 08, 2014, 08:53:39 AM

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

It does not fix the problem of quantity of transaction into wallets..... I mean dust coins

CPU itilization problem is triggered when there are hundreds of small PoS transactions. That wont happen if you increase PoS diff.

glop

full member

Activity: 126

Merit: 100

Quote from: primer- on July 08, 2014, 08:53:39 AM

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

It does not fix the problem of quantity of transaction into wallets..... I mean dust coins

primer-

legendary

Activity: 1092

Merit: 1000

...or just make it scarce enough! Higher difficulty + PoS after 3 months would fix it... Would also give us 3 more months to think about a new fix...

glop

full member

Activity: 126

Merit: 100

Quote from: slimcoin on July 08, 2014, 07:55:27 AM

If this is part of the PoS and cannot be changed/has not been yet fixed, I could make it so that PoS does not start automatically, but require an option like -start-pos, or something.

   A fix could also be to not split the transaction after calculation, something like:

   Verify if the coin is old enough ( 1 Week ? )
   then calculates the interest total= coins + interest
   then create the new transaction with total and then remove the old coins.


   Because the quantity of transaction is not only linked to POS but also POW can generates lot of dust coins, it could be also interesting to have a tool to concatenate coins automatically.

For example POS could be used as a regulator like,
if the coins value > high_limit then split coin
else if coins value < low_limit then if (next coin exist) concatenate coin with the next coin

slimcoin

full member

Activity: 182

Merit: 100

If this is part of the PoS and cannot be changed/has not been yet fixed, I could make it so that PoS does not start automatically, but require an option like -start-pos, or something.

glop

full member

Activity: 126

Merit: 100

Quote from: slimcoin on July 08, 2014, 07:40:02 AM

Yes, that is it.
But in that process, when does that happen?

Does it only happen when the coins are old enough, which is after the 1 week wait time, or when the coins can create a valid PoS block.

  I think when the wallet detect a valid POS block it launch this process ....

  The problem is not the quantity here it is the separation of the old transaction into two new transactions. It works on paper but not in real time.

   It was I think originally conceived to improve flow on the blockchain with a small amount of open wallet.....

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