WTS 15,000 Shinys for 12BTC
|
|
|
Can someone post a PoB block height or hash ?
|
|
|
Does anybody know a request/command to visualize how many block have been found so far with POB only ?
Not possible.
|
|
|
At least 15G of memory! Meaning: Most people can not participate
Where shiny future
Where is your plan
the worst part is that you need 32gb to mine at full potential, basically we need a server lol 16 GB is up to 16 cpu threads, 32 GB is up to 32 cpu threads, etc... If the # of cpu threads is >16 and isn't a multiple of 16, then you aren't mining at full potential. Read my post here https://bitcointalk.org/index.php?topic=655789.msg7420159#msg7420159
|
|
|
At least 15G of memory! Meaning: Most people can not participate
Where shiny future
Where is your plan
the worst part is that you need 32gb to mine at full potential, basically we need a server lol Exactly. My message about cpu utilization/ram usage got woooed earlier by the dev minions. He needs to fix the code so 15gb utilizes a single 8 core processor 100% instead of current 60%
|
|
|
People, don't forget that the "blocks" figure you are seeing in getinfo/getmininginfo includes PoB/PoS blocks. Actually there are a lot of PoB/PoS blocks mined ATM, so it's not accurate to look at the figure and compare it to the PoW blocks the pool has mined. Everything is fine. Your other IP is down : 92.222.27.45 / 3333
|
|
|
We need a standalone miner. No, i will not use a binary a random person on the internet posted earlier...
|
|
|
Its not possible to tell as the PoB is completely random
It depends of the number of coin you have burned, isn't it ? The more you burn the more change you get, so it is not really random ? There are random number of PoB blocks, so today the total of PoB could be 100 blocks and tomorrow only 50. Yes, how much you get depends on how much youve burnt, but there is no way to make an estimate as the number of blocks is random. Don't trust this guy Are you fucking stupid or what ? What i wrote is true. There are random number of PoB blocks per day. RandomSteve posted the list couple of pages back, it went like 200/250/150/220 (per day). Each block mints 19 or less by now. so yeah, GOOD LUCK with burning
|
|
|
slimcoin dev, my wallet with 4000 burnt coins is out of sync! its stuck at block 17625 (on both debian and windows servers). My other 3 wallets with less burnt coins are perfectly synced on the same servers. Something is not right here.......
Heres the debug
received block 00000003f3846bebbdea CBlock(hash=00000003f3846bebbdea, ver=1, hashPrevBlock=00000002f910b3d7c376, hashMerkleRoot=52454d6126, nTime=1403476901, nBits=1d0482f5, nNonce=6813, vtx=1, vchBlockSig=304502204034c4cd04bc4d1d2c2e8e46156bd23004db15ab98069e51ba9bedb6daae628e022100c2a835c2b335e14a7dd62b74258b2b832049c25a86561285f36e1d0f80b3a43e) CBlock General PoB(nBurnBits=1d01e92c nEffectiveBurnCoins=112384196909 (formatted 112384.196909)) Coinbase(hash=52454d6126, nTime=1403476901, ver=1, vin.size=1, vout.size=1, nLockTime=0) CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, -1), coinbase 02d944062f503253482f044b5ca75308280000ec020000000d2f6e6f64655374726174756d2f, nSequence=0) CTxOut(nValue=9.11, scriptPubKey=021037fe8a0bbec302fdab9ad08cb5dfef19fb8400ed515d5d3683b7be3edb0203 OP_CHECKSIG) vMerkleTree: askfor block 00000003f3846bebbdea 1403477903000000 SetBestChain: new best=00000003f3846bebbdea height=17625 trust=3196592552 moneysupply=279907.408375 nEffectiveBurnCoins=112384.196909 AcceptPendingSyncCheckpoint : sync-checkpoint at 00000003f3846bebbdead901b8a60e247bb88e98d76330f11151a016ceed9329 ProcessBlock: ACCEPTED SlimCoinAfterBurner(): Smallest Hash is 000000454fde0000000000000000000000000000000000000000000000000001 by tx 9b77b3ce12ea17ec183131e7de230f178817a05f809ca9ea7aa54cd9782001b5 with Block height 2218, transaction depth 1, vout depth 1 PoB Tartget is 00000001e92c0000000000000000000000000000000000000000000000000000 nBurnBits=1d01e92c, nEffectiveBurnCoins=112384196909 (formatted 112384.196909) getblocks 10322 to 00000003f3846bebbdea limit 1021 getblocks stopping at limit 11342 000000062f8e30a5c6dc getblocks 10322 to 00000002f910b3d7c376 limit 1021 getblocks stopping at limit 11342 000000062f8e30a5c6dc 2014-06-22 22:44:26 UTC Flushing wallet.dat Flushed wallet.dat 689ms Added 76 addresses from 107.181.250.216: 10 tried, 2998 new getblocks -1 to 00000000000000000000 limit 500 ResendWalletTransactions() Relaying wtx 43800e909b Relaying wtx e840370982 Relaying wtx aacb60dc83 Relaying wtx 379dc9f333 Relaying wtx c01dc0baac Relaying wtx 79b8cea7ca Relaying wtx 5d48405705 Relaying wtx 257dec886d Relaying wtx 3ccde649ee Relaying wtx 0fc4239dd5 Relaying wtx 3251f6925a
EDIT : It has synced for 5 minutes and is now behind again. Its as if its suffering from the same issue as the previous client ?? The only difference between this and other wallets is the amount burned - 4400
|
|
|
Its not possible to tell as the PoB is completely random
It depends of the number of coin you have burned, isn't it ? The more you burn the more change you get, so it is not really random ? There are random number of PoB blocks, so today the total of PoB could be 100 blocks and tomorrow only 50. Yes, how much you get depends on how much youve burnt, but there is no way to make an estimate as the number of blocks is random.
|
|
|
Its not possible to tell as the PoB is completely random
|
|
|
Sandor set up a script that restarts the wallet every hour or so..... pool was down for almost 2 hours..
Primer, curious why you bother with pools, isn't it more profitable to solo with your cpu power? Solo not possible due to the buggy wallet/rpcthreads issue
|
|
|
Weird, pool is not getting any blocks, something is wroing.. i'm stoping my hash...........
|
|
|
Sandor set up a script that restarts the wallet every hour or so..... pool was down for almost 2 hours..
|
|
|
Last block was found long time ago, i think its down..
|
|
|
0.0005 ?? Not selling below 0.002!
Primer-, SLM mades you bank again Hope so, we will see when bter opens
|
|
|
0.0005 ?? Not selling below 0.002!
|
|
|
@primer- Did you start your wallet with --rescan or try repairwallet in the debug console ?
Both, i also had a backup wallet on a debian box - same issue. It syncs up on both windows and linux (both qt and daemon) just fine but once i unlock it for minting it freezes! daemon and qt. linux and windows. Do you have plenty of free CPU and RAM on those PC's when your staking the wallet ? Have you tried downloading a fresh block chain with a blank wallet and then opening with the backup wallet ? Otherwise I would make several backups and try importing the keys as you have suggested. both have 16GB ram, i7 cpu. Tried everything you wrote, did not work How do i know which public key is associated with my burnt coins ? ok, i moved around 7000 coins from that wallet to an empty wallet and it no longer freezes. It seems like a lot of coins in the wallet + a lot of burnt coins on the same wallet = freeze
|
|
|
|