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

[Richard213]

interesting coin 

well, i will track this coin 

we will go to the sky , LoL 

[1714535977]

1714535977

[1714535977]

1714535977

[1714535977]

1714535977

[1714535977]

1714535977

[1714535977]

1714535977

[1714535977]

1714535977

[AizenSou]

i compiled slimminer for windows & ARM (cubieboard) and both have found a block. right now, I'm tryin to build it for ubuntu, but somehow my dev environment is messed up there ^^

Could you share your slimcoin.conf for solomine? Thanks.

my config:

Code:

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
rpcport=1222
addnode=76.127.202.17
addnode=96.237.174.192

i compiled slimminer for windows (...)

Would you share those binaries, please?

Or how you managed to do it?

Thanks

Oh well I use the rpcport 33700 from the OP. Maybe it is the reason. I will try the new port now. Thanks again.

[skottiejay]

Alright I'm sorry op, I'm gonna have to give up the ghost on this one. I've dedicated almost 24 hours to this. I know I can get better hashing power than what I'm getting, and I keep receiving dropped connections. It's an interesting concept but I'm wasting CPU power for things I could be doing otherwise. If you come up with a pool, or something that will ease this up for newbies I'll obviously keep a watch.

[ltcnim]

i compiled slimminer for windows & ARM (cubieboard) and both have found a block. right now, I'm tryin to build it for ubuntu, but somehow my dev environment is messed up there ^^

Could you share your slimcoin.conf for solomine? Thanks.

my config:

Code:

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
rpcport=1222
addnode=76.127.202.17
addnode=96.237.174.192

i compiled slimminer for windows (...)

Would you share those binaries, please?

Or how you managed to do it?

Thanks

Oh well I use the rpcport 33700 from the OP. Maybe it is the reason. I will try the new port now. Thanks again.

i compiled it under mingw for x86 with native cpu support. just download mingw, set it up and then follow the instruction on github for slimminer.

the port shouldn't matter. I just use rnd ports on my system which are not accessible from the outside. But which number you choose doens't matter.

[AizenSou]

the port shouldn't matter. I just use rnd ports on my system which are not accessible from the outside. But which number you choose doens't matter.

Yeah I know about that. But it is the only thing different from my setup with yours. So at least it worths to try.
Here is my getinfo

Code:

{
    "version" : "v0.3.0.0-g154b52a-alpha",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 3587,
    "moneysupply" : 69636.37140000,
    "connections" : 8,
    "proxy" : "",
    "ip" : "141.48.30.99",
    "difficulty" : 0.08949055,
    "testnet" : false,
    "keypoololdest" : 1401555054,
    "keypoolsize" : 102,
    "paytxfee" : 0.01000000,
    "errors" : ""
}

Could you share yours? Thanks  in advance.

[ltcnim]

i'm currently upgrading the server to a new distro. i will post as soon as I have everything up and running!

[reflector]

i'm currently upgrading the server to a new distro. i will post as soon as I have everything up and running!

Is this for a pool?

[rfcdejong]

the backend coding is going nicely for a PoB pool, i have most of the code for getting burn information from a wallet.
here a screenshot of the quick watch debug window on my own wallet

[primer-]

the backend coding is going nicely for a PoB pool, i have most of the code for getting burn information from a wallet.
here a screenshot of the quick watch debug window on my own wallet

Dont bother, no one is going to use a centralized pool for PoB. Thank you for the effort but no thanks.

[LIghtvelocityCoin]

the backend coding is going nicely for a PoB pool, i have most of the code for getting burn information from a wallet.
here a screenshot of the quick watch debug window on my own wallet

Dont bother, no one is going to use a centralized pool for PoB. Thank you for the effort but no thanks.

It's some kind of centralized BANK instead of pool.

[primer-]

It's some kind of centralized BANK instead of pool.

Even worse, centralized ANONYMOUS bank. Sure. Not gonna happen my friend. Please dont attempt anything similar again.

[rfcdejong]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

[JohnDorien]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

Its only primer crying as he's losing his burn chances asap a PoB pool is online..
I guess is you somehow manage to have all odds concentrated in a transparent system, you'll have loads of participants

[TheRealSteve]

I'd say continue your work - let those who want to use it, use it.  Anybody against the very idea can just, y'know, not use it.

[Stormbringer]

I would use PoW pool.

[qiuxiang]

This is what i got by listtransactions "*" true, please help me take a look, thanks

Open up your debug.log file and search for
SlimCoinAfterBurner():
              Smallest Hash is ....

SlimCoinAfterBurner():
   Smallest Hash is 000001283c40ad16ebcb3a6680ea9a3e5db023bb48d7e01d77848efa609de544
   by tx de71b3fff0e665d0086a684f6be11303551c7323e414dcac050ac615147b3c6d
   with Block height 1827, transaction depth 1, vout depth 1
   PoB Tartget is 000000064d5e0000000000000000000000000000000000000000000000000000
   nBurnBits=1d064d5e, nEffectiveBurnCoins=34075049630 (formatted 34075.04963)
getblocks 3454 to 00000004502126d1e969 limit 500
  getblocks stopping at 3455 00000004502126d1e969 (354 bytes)
Running SlimCoinMiner with 2 transactions in block
Running SlimCoinMiner with 2 transactions in block
getblocks -1 to 00000000000000000000 limit 500
getblocks 3454 to 00000004502126d1e969 limit 500
  getblocks stopping at 3455 00000004502126d1e969 (354 bytes)
Running SlimCoinMiner with 2 transactions in block
Running SlimCoinMiner with 2 transactions in block
getblocks 3455 to 00000004502126d1e969 limit 500
  getblocks stopping at 3455 00000004502126d1e969 (0 bytes)
Running SlimCoinMiner with 2 transactions in block
Running SlimCoinMiner with 2 transactions in block
Running SlimCoinMiner with 2 transactions in block
2014-06-01 15:44:59 UTC hashmeter   7 CPUs   3423 hash/s

This is what i get, thanks

In my qt, i see the maximum block is 3536, not sure why it says:
getblocks stopping at 3455 00000004502126d1e969 (354 bytes)

Hi developer or those who is familar with this, please help me to take a look, thanks.
I am worried that there are some problem with my wallet, or there are some problem with the codes

[primer-]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

Its only primer crying as he's losing his burn chances asap a PoB pool is online..
I guess is you somehow manage to have all odds concentrated in a transparent system, you'll have loads of participants

OK, dont say i did not warn you.

You intend to run a separate wallet for each user ? Good luck with that!! ))

Go code a PoW pool instead if you want to help the community.

[rfcdejong]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

Its only primer crying as he's losing his burn chances asap a PoB pool is online..
I guess is you somehow manage to have all odds concentrated in a transparent system, you'll have loads of participants

OK, dont say i did not warn you.

You intend to run a separate wallet for each user ? Good luck with that!! ))

Go code a PoW pool instead if you want to help the community.

The easiest would be just 1 wallet running on 1 instance. Until it has 1000 coins then i add another instance with a wallet that can go 1000 coins. I'm not sure yet, but if it has to be decentralized i rather run many worker roles. Foreach account 1 wallet makes it easier for statistics, because the burn decay etc is already build in for a single account then.

[reflector]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

Keep going man.  There are no maps for these roads.  Don't be dissuaded by fear.

[primer-]

That is not what i want, i want to setup a burning pool, finally existing out of 1 azure instance foreach account c.q. wallet. So someone creating an account will still have his own 'online' wallet. It is decentralized that way, payouts instantly after a PoB is found, automated, not in the online wallet, but to a user his own wallet which is out of the pool. The goal is to remove the gambling factor and let it payout to people. If there is no demand i can stop coding. Why didn't you guys said so at first   And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands.

Its only primer crying as he's losing his burn chances asap a PoB pool is online..
I guess is you somehow manage to have all odds concentrated in a transparent system, you'll have loads of participants

OK, dont say i did not warn you.

You intend to run a separate wallet for each user ? Good luck with that!! ))

Go code a PoW pool instead if you want to help the community.

The easiest would be just 1 wallet running on 1 instance. Until it has 1000 coins then i add another instance with a wallet that can go 1000 coins. I'm not sure yet, but if it has to be decentralized i rather run many worker roles. Foreach account 1 wallet makes it easier for statistics, because the burn decay etc is already build in for a single account then.

You are obviously a pool newbie. Please leave the work to someone else. If you want to help, go compile windows slimminer binaries.