You must use my slimminer fork : https://github.com/siklon/slimminer
Code:
./minerd --url=stratum+tcp://77.237.251.163:6666 --userpass=(SLMADDRESS):x -t (THREADS)
Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 162. (Read 284956 times)
June 01, 2014, 08:55:02 PM
Temporary pool : stratum+tcp://77.237.251.163:6666
You must use my slimminer fork : https://github.com/siklon/slimminer
You must use my slimminer fork : https://github.com/siklon/slimminer
June 01, 2014, 07:51:05 PM
hello, I find the OP quite lacking, isnt there some sort of guide to lead us through? ty!
June 01, 2014, 07:13:16 PM
this is a good coin, i will mine it now
June 01, 2014, 06:49:59 PM
4 days have passed since launch – as there's no block explorers and the like yet, here's some basic graphs
(if you want to ask anything about a specific graph, please only quote that graph (or refer to it by title), as these posts are relatively big)
(if you want to ask anything about a specific graph, please only quote that graph (or refer to it by title), as these posts are relatively big)
 |  | |
 |  | |
 |  | |
 |  | |
 |
Explanation of graphs: topic=613213.msg7044755#msg7044755
Like this post? Donate Slimcoin: STDpqwvEC6banMNzfNYDTuZy8xspHpGuNj
June 01, 2014, 06:06:03 PM
I'm getting error. "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
Make sure you've got the addnodes list set up - see first post.Fixed.
Just port forwarding issue. Thanks buddy.
June 01, 2014, 05:50:16 PM
I'm getting error. "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
Make sure you've got the addnodes list set up - see first post. 
June 01, 2014, 05:26:58 PM
I'm placing a 0.1BTC bounty if someone reputable compiles the following :
- Static linux binaries (slimminer, slimcoind and -qt), compatible with glibc 2.5(so it works on both old and new linux flavours).
- Windows x64 and X86 binaries (slimminer)
I'll drop another 0.1btc bounty if someone comes up with a patch that lets the wallet mine PoW when encrypted.
- Static linux binaries (slimminer, slimcoind and -qt), compatible with glibc 2.5(so it works on both old and new linux flavours).
- Windows x64 and X86 binaries (slimminer)
I'll drop another 0.1btc bounty if someone comes up with a patch that lets the wallet mine PoW when encrypted.
June 01, 2014, 05:25:59 PM
I'm getting error. "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
June 01, 2014, 05:18:48 PM
I burned a day, did not get any coins
This is my conf file, right?
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
addnode=144.76.142.47
addnode=144.76.142.49
This is my conf file, right?
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
addnode=144.76.142.47
addnode=144.76.142.49
June 01, 2014, 04:46:46 PM
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.
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.
June 01, 2014, 04:45:43 PM
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.
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.
June 01, 2014, 04:41:09 PM
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.
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.
June 01, 2014, 04:35:49 PM
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.
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.
June 01, 2014, 04:35:20 PM
Quote
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
June 01, 2014, 04:30:47 PM
I would use PoW pool.
June 01, 2014, 04:29:04 PM
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.
June 01, 2014, 04:28:10 PM
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.
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
June 01, 2014, 04:24:43 PM
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.
And yes, trust has to be on me, not anonymous.. google my name, find my work or even my house in the Netherlands. June 01, 2014, 04:13:22 PM
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.
June 01, 2014, 04:11:56 PM
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
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.
Jump to: