 Show Posts
|
|
Pages: « 1 [2] 3 »
|
|
Still need a few more players to get the rounds rolling.
I can up the anty a bit for you all; For every ticket you guys buy, I will eat/save a kitty. The winner gets to choose.
|
|
|
|
www.rafflebit.comCurrent pot is > 4 BTC! Buy as many tickets as you want and play the odds! Prizes for 1st, 2nd, and 3rd place winners.
|
|
|
|
We spotted a couple of more bugs and got them fixed. Currently pot varies from 1-5 BTC. Beta is coming along smoothly, thanks for the help. www.rafflebit.comGo win some  |
|
|
|
|
We have updated the pot size to help finish off the beta process. The pot sizes were to small creating rounds that were to fast and not well balanced.
New pot size varies from 1-5 btc.
Have fun playing.
|
|
|
|
|
Look us up if you want to stay up to date on beta progress, when introduce new features, and to toss us your thoughts.
Facebook: RaffleBit
Twitter: @RaffleBit
|
|
|
|
|
It's a fresh lightning round of RaffleBit is up!
Buy your shares for a chance to win some Bitcoin!
|
|
|
|
|
These rounds are going pretty fast. The current pot is 50% of the way purchased. You should have good odds of winning right now since the pot totals are kept small for the beta!
|
|
|
|
The current round has already sold over 2/3 of the shares available. Hurry up and purchase your shares so the winner can get to their happy ending  |
|
|
|
|
We are working on that, in the mean time, try swapping web browsers and see if that works for ya.
|
|
|
|
www.rafflebit.comHey Guys, Although the project itself is not done, all the programming for functionality has been completed and would like you all to help test it out. To help things go quicker, the payout on the raffles has been shrunk down to create faster games for testing purposes. Check it out and feel free to leave any feedback. -HM
|
|
|
|
1 What other fields can we change in the message when mining, other than the nonce? The timestamp, the coinbase transaction, the list of transacations included in the block. 2 Where is the extraNonce located? My recollection is that the 'extraNonce' is the coinbase. See here where its put into the input of the coinbase transaction: pblock->vtx[0].vin[0].scriptSig = CScript() << pblock->nBits << CBigNum(nExtraNonce); pblock->hashMerkleRoot = pblock->BuildMerkleTree(); 3 Where is the time (and can we change it as we see fit while mining, or are we required to keep it in a certain range)? The time is in the header, but it must be kept in a sensible range. Good answers. I was just gonna say work with 6 other dwarfs and capitalize on woman work. |
|
|
|
Unfortunately we recently discovered that our database (essentially a list of addresses and the block number in which they first appear) was missing part of several blocks. We took the site down to recheck the whole database and add some checks so that it can't happen again.
Does this mean our firstbits are no longer valid? |
|
|
|
Do you have insurance to be practicing engineering or is your work uninsured? Are you licensed/registered?
MDKing
"Engineering in the UK is not a licensed profession. In general, there is no restriction on the right to practice as an engineer in the UK" So the answers to my questions would be your work is uninsured and you are not registered with any of the engineering bodies, such as Engineering Council UK, as a Chartered/Incorporated Engineer? 10 Points great, made my day |
|
|
|
as I understand, a wallet is not really a wallet, but a key. This suggests it can be shared between computers. Meaning if I have my wallet.dat copied from box A to box B and both boxes run the bitcoin app, box A should pick up the transactions from B and vice versa so both always show the same balance (not counting network latency). Is this correct?
If I understand BTC correctly that would be correct. It is essentially running your backup on another computer. This would go fine and dandy until you started generating new BTC addresses to receive with. Both wallets would start generating different addresses so coins received in wallet A would not show up in wallet B unless you made all the addresses in wallet A then mirrored it to wallet B. Long story short, it's the same until you start generating addresses. This is why it is also important to back up your file periodically. If you generate a bunch of addresses, start receiving BTC from them, lose the wallet.dat, restore an old backup missing the new addresses, those coins sent to the new generated addresses that are not on the backup are lost to the void, never to be seen again. |
|
|
|
|
agreed
who the hell still uses metal these days? teenagers?
|
|
|
|
I wanted to tip the OP for his good idea, but there was nothing in the sig  |
|
|
|
I am game for free coins |
|
|
|
|
I am interested, PM with info. Thanks.
|
|
|
|
|
