come along, step right up for these valuable shitcoins  now also listed on yobit |
|
|
|
i have 200 HVCO received for building mac wallet, these are now up for auction they're sitting on empo-ex which charges a 0.1 tx fee leaving 199.9 HVCO (unless they have user codes which i can't see so probably not) bids are to be in BUMBA COIN. rules-
auction will last for 3 days (ish) ending June 18 at 12:00 pm.
bid by adding a post in this thread with your bid value in BUMBA.
last post before ending time with highest bid will win.
see this thread for interactive bidding goodness https://bitcointalk.org/index.php?topic=1512804.msg15219092#msg15219092 |
|
|
|
 i have 200 HVCO received for building mac wallet, these are now up for auction they're sitting on empo-ex which charges a 0.1 tx fee leaving 199.9 HVCO (unless they have user codes which i can't see … so probably not) total coin supply 823225.0005bids are to be in BUMBA COIN. -- HVCO thread : https://bitcointalk.org/index.php?topic=1489677.0   it also just won the latest Cryptopia crowd vote so should be listed there soon enough .. -- rules-
auction will last for 3 days (ish) ending June 18 at 12:00 pm.
bid by adding a post in this thread with your bid value in BUMBA.
last post before ending time with highest bid will win.
winning user should PM me with address  -- get BUMBA
here https://www.cryptopia.co.nz/Exchange?market=BUMBA_BTChttp://bumbacoin.com |
|
|
|
My holdings are around 110,000 Reiki found both pre and post (July 2014) fork through a combination of mining and staking. While I wish Reiki Coin well, I don't want to create animosity with the wider community and will bow out of further pushing for the "357 Chain".
I'll leave the blocks up on Mega and MediaFire for research purposes.
i guess we'll keep mining on the "new" chain then as things stand then █ the clients compiled previously seem to lack any problematic checkpoints so they seem fine to use as is. █ any new clients compiled from "official" source will have problematic checkpoint, for any new compiles there are two choices1. remove checkpoint from source for block 357000 (or comment it out) https://github.com/ReikiLVL3/reikicoin/blob/master/src/checkpoints.cpp#L292. use the git i created, it has new checkpoints matching the current chain https://github.com/bumbacoin/reikicoin█ it will probably be advantageous to create a new thread and compile new clients with the updated checkpoints, i've been quite busy of late so have only been peripherally interacting here, i might find some time coming soon (i hope) and i can put some effort into looking at the code and arranging some new clients.. i also can send you, RussiaCoinDotInfo some reiki as i seem to have mined a few  i wonder if the reiki master still thinks of us |
|
|
|
curiously the chain is currently disconnecting PoW blocks. i've been mining for the last little while, i get blocks, then they disconnect in favour of a PoS block. i went back 200 1000 blocks on the explorer and they 're all PoS blocks. (here's the last PoW block) http://146.185.162.58/reiki/rpcace.php?339373the explorer displays these PoW blocks until they're disconnected from the chain. http://146.185.162.58/reiki/rpcace.phpedit. i mined a few blocks that are still there. although it's gone back to staking all the blocks now and disconnecting the PoW blocks i imagine the PoS block outweighs the PoW block for difficulty hence the disconnecting of those blocks .. but then i assume then that the staking client is unaware of my PoW which is the actual curiosity that the client is staking generally obliviously to the erstwhile PoW blocks |
|
|
|
Problem with syncing.
Wallet stands at block 151582 and not moveing. Telling 19H till sync.
Any solutions?
at a guess, i'm assuming it's just a matter of mining (or not mining). the 19 hours is a guesstimate from previous block times and targeted block time, so if no block has been found in a while, even though you are in sync, the wallet expects more blocks (which are not yet existent). what you could do, is stop and restart yr client, go to debug console and type getpeerinfo then you can see "startingheight" of other peers, and compare yr block height against other peoples... |
|
|
|
|
and some more shitcoins.
lol
bit over them tbh :p will now request bounty upfront or possibly payment in BUMBA.
|
|
|
|
|
please. give me all your fwee.
thank you.
|
|
|
|
thanks have received funds |
|
|
|
Do you suppose a second block chain can reach the check point 357,000 and come up with the same check point block?
the hashes are based on previous block hash and other block specifics. i don't know whether it's possible to generate the same hash for completely different blocks, but if so, it would be as unlikely as putting your finger through one ear and wiggle it out the other. (i.e. it would involve some hefty manipulation of yr head. lol) in other words, no.
any opinions on which chain to go with?
i personally think the 2nd chain from johan11, - the coin must have been pretty dead for it to fork so badly, no-one even seemed to notice until now. - without johan11's effort the coin would be well dead. - i'm all up for a fork to lower min stake age to create a more manageable chain with lower PoS requirements, atm PoS blocks have no hope in moving the chain usefully and it seems 90% (heh made up figures ftw) reliant on PoW any fork will require a new git and new thread which will also assist in getting rid of the "bad" checkpoint. i also personally think this coin is unlikely to survive even with this effort so it's more fun than anything else. heh, unless the dev notices this activity and decides to show up after this long.. |
|
|
|
in blockexplorer in height 283883 is time
1425178261
GMT: Sun, 01 Mar 2015 02:51:01 GMT
lol oops. fixed earlier post so, a goodly time between blocks .. nearly 8 months |
|
|
|
post yr chain up somewhere. and we can see how it looks .. i'm surprised you're staking though, means someone is on the same chain as you? or you have two clients with different chains |
|
|
|
OK. First I typed getblock 4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805 and got {
"hash" : "4e7666bb31c44138b41c78b06b170075ad1d0180108bc8b9bd7e71d2f49d7805",
"confirmations" : 10127,
"size" : 459,
"height" : 357000,
"version" : 4,
"merkleroot" : "a65873dcf0d1153f0d69b8ef4771e96d7e1cd409d9692c8982e92d2f247364e8",
"mint" : 3.77064600,
"time" : 1415579531,
"nonce" : 0,
"bits" : "1e00ff1b",
"difficulty" : 0.00391989,
"previousblockhash" : "0000000001cf3057d98c5d922a515d64e49cdbfdec7d273dd328394c88ea942c",
"nextblockhash" : "c72e40ce3896196222cf05bf77497a0fb1cd3433046e563b414ed8465126d8d0",
"flags" : "proof-of-stake",
"proofhash" : "00008cd2666fbcdcc68ee9e252eccebecced903e5011e3b591cc5571089222c1",
"entropybit" : 1,
"modifier" : "dbe1721f51c5498e",
"modifierchecksum" : "c2e14e59",
"tx" : [
"6c89ab3771a3f1eab82c770ded6b9765aa0145e4a55e367a90995e28ae78268b",
"d5580f23ecd55da492f8ed95166b7214d5a0093d884a60d6eec06d6c9757963d"
],
"signature" : "3046022100cf5049fade6076997848a07e99e991d40ebaf37a608e024d61d1e01398d3bd8f022100802cb7f62fda1eb0b58776b5af4063da3e95026e1d70b18300af4061ff5821dc"
}this … basically the situation is that a major fork is currently excitingly in our midst. the chain held by RussiaCoinDotInfo matches the checkpoint on the official hub, BUT has not been touched for over 12 months? the chain currently mined by myself and Johan11 has been running since at least may 2015, but is incompatible with the official source on github. . if we were to go with 1 - the chain matching official hub. that would destroy over a year of work that has potentially important transactions on it - however given the lack of exchanges or major infrastructure it probably does not matter. if we were to go with 2 - the chain kept alive. that would mean the official git is a problem, would need a new thread AND new git. also would meant the loss of a lot of other legitimate work on the chain .. johan11 has put the most work into this over the last year and is running chain number 2. |
|
|
|
in case anyone hits this error running new qt Error initializing database environment /Volumes/datarer/COINZDATA/stepsDATA!
To recover, BACKUP THAT DIRECTORY, then remove everything from it except for wallet.dat.
basically that's saying there's a database incompatibility between versions and will need to be rebuilt. you'll need to resync from scratch using existing wallet.dat backing up stuff first for safety delete everything except yr wallet.dat and start, it'll connect and sync by itself .. edit, oh, you can use yr existing chain as a bootstrap. when deleting everything (except wallet.dat) also keep blk0001.dat, then rename as bootstrap.dat the client will import chain from the bootstrap rather than downloading it. further edit, possibly the old wallet.dat is not compatible at all, there are some reports of a corrupt wallet.dat. there are two ways to update, one - using the wallet.dat, two - importing the private keys to your addresses, if you need help to import the privkeys please post in the thread here, and access the community support |
|
|
|
|
Show Posts
