|
Can we crop out that dude's package ? ? ?
|
|
|
|
I thought I have seen Gavin somewhere talking about adding fees to already existing transactions... am I mistaken ?
I'm working on a patch that will create the basic infrastructure to add fees to transactions that have been sent but not yet included in a block. It will only let you add additional inputs and outputs, but never make any output have a lower value than it did before. Nor will it let you modify a transaction that has already been spent. I've been considering what criteria nodes should have to allow discarding a pending in-memory transaction and replace it with an increased-fee transaction. Your conclusion is logical. Since the output of a transaction that is change can't be identified by miners or nodes, to validate what constitutes a legitimate non-double-spend transaction, it appears that a retransmitted transaction must not alter any inputs or outputs in the original transaction. If one of the outputs were allowed to be reduced to increase the fee, this could mean a 0 confirmation payment to someone could be changed from the expected value, which is the definition of a malevolent double-spend. If any output could be modified in the original, this means that 0 confirm payments could not be trustable, because output values could be moved from one recipient to another or reduced. Instead, fee must solely be added by adding a new input, and a separate change payment must be sent. In the example below, I show where we add another complete input and change (where fee = input - change).  OutputX, another payment to another recipient (or a third change payment to enhance anonymity even more), could be optional and shouldn't be a "blocker" if it exists. Change from adding a fee demands some new outputs. However, being able to add such "mini-transaction" chunks with new inputs and outputs and retransmit them, could mean that a service that issues many regular payments could just keep adding to an existing 0 confirmation transaction and retransmitting, instead of creating a new transaction. I don't know if this would be a novel feature or undesirable. Another strange situation is if the original tx has spent all the available inputs, the user can't increase the fee. Explaining why the wallet can't add more fee even though it shows a balance will be one for the UI designers. |
|
|
|
This is what you are agreeing to on the site (I seperated the sentences so it becomes barely more readable): Bitcoinpride.com Design Submission Legal Terms & Conditions Last Revised March 6th, 2013 By selecting "I Agree" below and in consideration of bitcoinpride.com evaluating your Design (hereinafter the "Design") for its possible use on clothing and future product graphics (the "Items"), you agree to the following terms and conditions ("Design Submission Terms and Conditions"): If your Design is selected for use by bitcoinpride.com, you acknowledge that you assign to BitcoinPride and its subsidiaries and affiliates (hereinafter collectively "bitcoinpride.com") the entire right, title, and interest in and to the copyright in your Design including the right to sue for past infringement and the right to further sublicense the Design, for its sole and exclusive use on and in connection with the Items. You also acknowledge that you waive all "moral" rights that you may have in and to your Design. If your Design is selected, bitcoinpride.com may use your Design in any manner on or in connection with the Items, including but not limited to: reproducing the Design on the Items, selling Items bearing the Design, changing or reworking the Design by making color or size changes, making derivative works of the Design, using the Design on the bitcoinpride.com website and on promotional material for bitcoinpride.com, and registering the Design with the US Copyright Office in the name of BitcoinPride as the Claimant, and you as the Author. You agree to provide bitcoinpride.com with minimal information as may be required in order to register the copyright in the Design if bitcoinpride.com so requests, at no cost. You may use or continue to use the Design for any other purposes, except those described below. If your Design is selected, you may not use the Design (or derivatives of the Design) or allow others to use the Design (or derivatives of the Design) on any Items, as described above. In addition, by submitting your Design, you may not reproduce, sell, or submit the Design to others for any commercial purpose for ninety (90) days after the date of submission while the Design is being evaluated by bitcoinpride.com. Once the ninety (90) days have passed, if your Design is not chosen for print by bitcoinpride.com, you are free to use the Design for any commercial or non-commercial purpose. However if your Design is used elsewhere, you must notify bitcoinpride.com by email at support@bitcoinpride.com about where and when the Design will be used, so that it can be removed from the bitcoinpride.com website at that time. In addition, if the Design is used or reproduced for commercial purposes elsewhere, you cannot use the bitcoinpride.com design page to promote the Design or the company using the Design. You further agree not to use the bitcoinpride.com design page to promote the products and services of any company that operates in competition with bitcoinpride.com. Bitcoinpride.com reserves the right to choose your design after the (90) days have passed, on the condition that the design has not been used for commercial purposes on any Items, as described above. You acknowledge that the Design you are assigning to bitcoinpride.com is your own original work, has not been previously published, and does not contain any trademarks, logos, copyrighted material, or any other intellectual property belonging to any third party, or any material, which bitcoinpride.com in its sole discretion, deems to be profane or offensive. You acknowledge that bitcoinpride.com reserves the right to decline to select a Design for consideration for any reason, including poor design, as further explained in the "Decline Reasons" page of the bitcoinpride.com website, which are subject to change at any time. If your Design is selected for use by bitcoinpride.com, you will receive: $250 cash/BTC and a $50 bitcoinpride.com Gift Certificate. Bitcoinpride.com reserves the right to change these payment terms at any time, by posting them on the bitcoinpride.com website, and changes will be effective upon posting. Payment will be based on the terms in effect when your Design is selected. You alone will be responsible for the payment of any tax that arises as a result of receiving payment from bitcoinpride.com. Payment will be sent within ninety (90) days after bitcoinpride.com receives hi-resolution artwork deemed suitable for print. If the hi-resolution artwork is not deemed suitable for print as determined by bitcoinpride.com, bitcoinpride.com will notify you of the reason(s) for its determination by email and will make a good-faith effort to assist you in presenting a suitable hi-resolution format. Participants, who in the opinion of bitcoinpride.com, do not comply with these Design Submission Legal Terms and Conditions, or for any other reason at bitcoinpride.com"s sole discretion, can at any time be excluded from consideration without notice. The decisions of bitcoinpride.com are final and binding. This is an untenable contract. You demand people not use their work for 90 days, when they have neither assigned any copyright or license to you, nor entered into any compensated arrangement. Unenforceable. You want to sue people for "prior use"? So the person that uploaded the "rendered bitcoin logo" (who is most certainly not the creator) in some way gives you the ability to sue reddit or other places it was used, or even sue the uploader or creator for their own prior use of the artwork? You can change anything at any time? So after you get stuff uploaded to your site you can change the terms, like the contest reward is now 0.0001 BTC and everything uploaded becomes "selected" and the copyright is transferred to you, or even easier, "anything previously uploaded is now ours to use in perpetuity"? Hell no. I recommend people stick to what they've been doing, uploading the copyrighted works of others. Domain providers like to take down not just domains, but entire domain accounts, when they get DMCA notices. |
|
|
|
so was given already the bounty here? i was pretty amazed trying to win it and finally looks like this thread died
No bounty was paid, just a thread of wasted effort and lies from Phinneus Gage. "This thread contains an offer of 1 BTC. If you can figure out how to get it paid, good luck to you."  |
|
|
|
Replying to PM here for the benefit of all: I've tried the -salvagewallet command but it didnt do anything other than close the client right after it started. Afterwards I looked for the String "keyA" which I could not find either. Is there anyway of recovering this wallet you think or should I just drop it?
(note: this wallet is about a year-ish old and I backed it up on a flash drive, a while later my laptops HD died and lost the 2 BTC but still had the wallet.dat which I forgot about. Accidentally I deleted it and a few days ago I undeleted it using a software to recover that. Maybe thats why its corrupt?)
Undeleting a file in a file system that has no such inherent feature will "restore" whatever is occupying the sectors and blocks on the hard drive that previously contained the data. If subsequent disk activity caused data writes, the disk space might have been overwritten, and what you recovered is not the original data. If the only copy of the wallet was on a flash drive, and you deleted the copy that was on the flash drive, then you should have used specialized flash data recovery tools to get data off. I just created a new v.8 wallet.dat, and found that upon generation it did not have the string keyA in it, although it obviously had at least 100 private keys in it by default. What it did have was a size of 80kB, and a bunch of the word "pool" in it ( 01 04 70 6F 6F 6C ), this looks to be a better test to discover whether the data is really some wallet data or random hard drive garbage. The data around "pool" entries in the wallet might look like this: 000076d0h: D3 12 C1 08 0D 00 01 04 70 6F 6F 6C 07 00 00 00 ; ......pool....
000076e0h: 00 00 00 00 D7 00 01 D6 30 81 D3 02 01 01 04 20 ; ......0....
000076f0h: 99 D9 7D 0B 46 E4 83 73 FA D8 32 A3 44 52 D5 60 ; }.Fs2DR`
00007700h: 4F 9C 30 9D 71 50 6A 16 DE 4E AA 97 11 AB 19 A3 ; O0qPj.N..
00007710h: A0 81 85 30 81 82 02 01 01 30 2C 06 07 2A 86 48 ; 0...0,..*H
00007720h: CE 3D 01 01 02 21 00 FF FF FF FF FF FF FF FF FF ; =...!.
00007730h: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ;
00007740h: FF FF FE FF FF FC 2F 30 06 04 01 00 04 01 07 04 ; /0........
00007750h: 21 02 79 BE 66 7E F9 DC BB AC 55 A0 62 95 CE 87 ; !.yf~ܻU b·
00007760h: 0B 07 02 9B FC DB 2D CE 28 D9 59 F2 81 5B 16 F8 ; ...-(Y[.
00007770h: 17 98 02 21 00 FF FF FF FF FF FF FF FF FF FF FF ; ..!.
If the flash stick is the only media that might contain the wallet/private keys, then I would recommend you follow the recovery options here to scan the whole storage device for keys: https://bitcointalk.org/index.php?topic=38004.0 |
|
|
|
So you are quoting yourself to show that you found your answer earlier in this thread?: Does anyone have a full copy of the 225453 height blockchain fork or a novel way to recreate it? I should have been clever and made a copy of my datadir while this was going on. For testing, one can --connect any clients to an isolated node using this fork at that height, although I think any inconsistencies between versions/build environments (why were some <0.7 ok with the fork?) will come down to platform BerkeleyDB defaults. |
|
|
|
|
This is incorrect advice. Users do not need to do anything now that the fork is resolved. Their current version of Bitcoin will work just fine. The only action needed was for a handful of mining pools to change their software to promote the desired version of the blockchain (and disable the creation of huge blocks).
|
|
|
|
As a professional software developer this may be an opportune time to point out that the bitcoin code is an amateur production. As an amateur forum user, this may be an opportune time to point out to others the ignore button. |
|
|
|
This payment from MtGox was paid without fees even though the priority demands fees. This is par for the course, other MtGox green address withdraws have had the same experience of MtGox paying no fees even when they are required: https://bitcointalk.org/index.php?topic=75813.msg858890#msg858890Completely the opposite behavior of that which is desired - a green payment should be trustable as a zero confirmation because MtGox is supposed to be "trustable" not to double-spend, but they are LESS trustable because no fees are being paid. March 12, 2013, 3:33 a.m. ed2bb18f1ca80730a3ce4abf69bbce19805a20b4d0bf6c5c1e26e7082e3f855e
This is a low priority transaction.
size: 257 bytes
priority: 17,023,064
input: 2.57348671 BTC
fees paid: ab-so-fucking-lutely nothing
2.57348671 BTC from 44106d7b2986fc7c8ee10683a1ba991b3c7b6c379409746a630d01e20bcd6b53:0 (1LNWw6yCxkUmkhArb2Nf2MPw6vG7u5WG7q)
output: 2.57348671 BTC
1.50000000 BTC to 1QARSgpZ2um4n9JFBhMYTxBYXZsxEhEUb6
1.07348671 BTC to 12M7oXubEqhh4qkWhtKVX2BF1mAShKi2cqYour payment might be included in the blockchain sometime after the other 2MB of pending transactions that are also discardable dust. MtGox likes to not pay fees at the expense of users - send a private key sweep address a satoshi, and they'll send out a 0.0000001 auto-transaction with no fees that will be discarded by miners and relayers. |
|
|
|
Thank you all for your help, but I just found out that my backup wallet.dat is somehow corrupt, and Bitcoin-QT cant read it  If my above steps didn't work (where you get an error "corrupted wallet"?), these additional steps might get data out of the wallet (using Bitcoin 0.8.0): -close Bitcoin, have your backup wallet.dat in the data directory. -rename the "database" subdirectory in the data directory -start bitcoin with this command: bitcoin-qt -salvagewalletIf there is still no joy, you should attempt to open the wallet.dat file with a hex editor and see if there are multiple instances of the string "keyA" in the file (the private key is right after this string); if there is no "keyA" then the data is not a recoverable wallet. I can see if there is any hope of recovering the wallet.dat and send you the recovered Bitcoins if none of these work - contact me via PM for a secure method to send me the best copy of the backup wallet and I'll see what can be done. |
|
|
|
And there it is...
Tempest in a teacup. I've personally seen much, much worse episodes in commercial software products and financial services. All will be totally forgotten by general public within 30 days, max. I had to deal with a "small" y2k problem that wasn't caught - battery backup software wasn't y2k compliant, so at the turn of midnight, the software (which is supposed to gracefully shut down computers if the power goes out) started turning off every point-of-sale computer, and would continue to turn them off five minutes after they were turned back on. I think there were about 3600 or so of those deployed in all 50 states. Try to remotely manage computers that are off... |
|
|
|
Is there any way us mere mortals without minig rigs can help? if we all come online with version 0.7 will it help or just create excessive traffic? If you're not mining there is nothing you can do to help, and there's no reason to downgrade to 0.7 if you already upgraded earlier. I meant those of us with a half decent Graphics card can start mining on 0.7 to process the right chain, But in all probability with my set-up re-syncing the blockchain would take more traffic and by the time my client caught up I think the blockchain race would be over. Just mine for a pool like ozcoin.net getwork that is mining the new chain. us.ozco.in:8332 |
|
|
|
So just to be clear, the only lost coins were those mined using 0.8 since the fork?
Generated coins are not mature for 120 blocks, so they were never spendable by the miner anyway. Some pools might have some sorting out to do in their accounting systems though. |
|
|
|
Block progress - bad chain height = 225453; good chain = 225445, another hour + to go before the BIG REORG! Soon to be orphaned: 000000000000015c50b165fcdd33556f8b44800c5298943ac70b112df480c023*225430
00000000000002d2012cc1b3fc0cceb8c156f0e698db40bf4413a210eca056c3*225431
00000000000002c9e42c23f6eed2b9f9152a440610dcfaf992357c3cbff3689c*225432
00000000000001b3c862fd66689712bc1cdd44fc004c008ada6c1b51367686f2*225433
00000000000002528688a366a9f42c07089268cd8a474961c49f787cb385807e*225434
00000000000000947452b814ed008f750023e64c8fd03bb19b3865716eeb243d*225435
00000000000001a23b3f38106f210493795a1ef6b21dd559f87ada8dfc84181b*225436
000000000000000016b3a292d63f9eea6b8177b8ba8dfd621d36fd828e5cb187*225437
000000000000019881625f04eac2046512fa1e1bd7193f56f39595d802bbbd04*225438
000000000000015aab28064a4c521d6a5325ff6e251e8ca2edfdfe6cb5bf832c*225439
00000000000003264ac7a6a74ca779997ee637b30f84debcb6ba6c26e2d09f4b*225440
0000000000000372a4c37e27587255ca77a6377391c1974f13ea55ec1d3bc01b*225441
0000000000000229cd059490b7607ca4c191c52bb40405fa052c48d72bfda8b0*225442
0000000000000213874009d269b90be16ea5c1f6a83a79ae2be3813d8972a2a3*225443
00000000000003381ed79de2fa810c0e4f0e9c0cd5d307380b779e2b5ffa982e*225444
00000000000000ec0df675972dddf0c2bdb1d436064672a6f0b79ce65ffcade6*225445
00000000000000757de9173ee2f01c9f957c8aa3b4f71b901b0fa19683ab1fa1*225446
00000000000000ec24f812807f81aadb7a665ef4ab8b8aa49df5ef789cdc13ff*225447
00000000000001f9fd0b0cab82deca5f53030911b33ba7dd7ce3fd77ad2c5a55*225448
00000000000001f15726ea57dc7702407a3ebc097ed801cb3d7b0e8a450807cb*225449
000000000000026a105de544bfbe71bca0820ac3963ba132c75ec40411b5f162*225450
00000000000003bdcc4424dea94de83e9f54ca158ae3eac59c2e97c2f90a32ad*225451
0000000000000190f5944e56c52600e9d8d4d5416432e03b324bc85c51629bcd*225452
000000000000031803e492a0103154d243c9945ef78dbdba42a1ecfdb5bc5dbb*225453 New 0.7-created blocks 00000000000001c108384350f74090433e7fcf79a606b8e797f065b130575932 225430
00000000000000f2c09bd58b84a7ef33fbc038a6fed97c072643b1e61d8ab841 225431
00000000000000362b16136f026a99ed5c59c0a4dc99e60fe87c28f3220438d6 225432
0000000000000040fcdf075576b52f2f83d852e4f356936645bcb4e745c94e15 225433
0000000000000105d2e2b2d0501ad1826bbd622c044fb77c865f98fce4781106 225434
000000000000027373b3fa7b123ca461e5c5d090c9caeb24a8bbbd32e1eaaa5d 225435
000000000000016e4bbe5cac005375b3dd799839c4b430959158b645b2dbafae 225436
000000000000022500c140cbc4ba13eebeb9859b08461c7a35fb233202ec8374 225437
0000000000000307714abe653fc80e966eca3bfe94e74697b5ec611b3c23ab96 225438
00000000000002b63d8aa07404d752703d12bf8b58a7663de30c71c719f9b2ce 225439
0000000000000025fcc0c001b11e542ae73dc4d9edc9ed9d82627563a2af5d81 225440
0000000000000133ecdb94ba8017e2977aefe3e497c48c849e3f9c4c7a091564 225441
000000000000003d3e6473a13a33ed9419bf3863d08c62e2a67abae871e2fac9 225442
00000000000001a2a869f12fab167b3506407cb62f16ff8e316a1d7b7cbd9d56 225443
000000000000007b7879107d003317325df8b3772a73f7a1c179ed99cb9d04b2 225444
000000000000012966aca980b406faa35b4c7abcc896846794f2c3f6f9b63aa0 225445 Zee blockchain killer 225430 (slush / 1MB): http://blockchain.info/block/000000000000015c50b165fcdd33556f8b44800c5298943ac70b112df480c023Current best of new branch: http://blockchain.info/block/000000000000012966aca980b406faa35b4c7abcc896846794f2c3f6f9b63aa0 |
|
|
|
|
You can send the bitcoins from the old wallet to yourself quite easily:
1. get a receiving address from your wallet (like in your signature)
2. shutdown Bitcoin
3. rename your current wallet to wallet.dat.newestwallet
4. copy the old wallet to the bitcoin data directory
5. start Bitcoin, and after there are some connections, send the balance to your address
6. leave Bitcoin running until you get a confirmation
7. shutdown bitcoin, rename wallet.dat to wallet.old-empty and put back your original wallet
8. Start Bitcoin and see your new balance
|
|
|
|
Unless you have an ATI Radeon Today is more like "Unless you have an ASIC"  OK, other miners:  |
|
|
|
Unless you have an ATI Radeon HD 5xxx GPU or higher, mining will cost you more in electricity than you will earn. Even a $380 video card will make you just 0.06 BTC a day. Other miners:   You:  |
|
|
|
Can't you send payment like, every 30 seconds?
Put together a list of all bets and send the winnings in a sendmany.
That would reduce the number of transactions a day and the size of the blockchain, I think.
And 30 seconds is still pretty fast IMO.
That results in a transaction where everyone who received a payment in it must spend their dust before the transaction can be removed. Future optimization of clients will allow disk space to be reclaimed after a transaction is spent (see chapter 7 http://bitcoin.org/bitcoin.pdf), so creating transactions that are hard to spend or never will be spent is bad. The endgame for many gamblers will be to lose all their money and be stuck with a gambling wallet with hundreds of dust payments. By making the loser dust large enough that it can pay it's own minimum fee to send it, someone can spend the balance of a wallet - it might cost 0.1 BTC in fees to empty 0.11 BTC of dust, but that's better than 0.1 BTC in fees to send 0.0001 BTC of dust (deleting the wallet and starting over would be cheaper and easier). If SD paid .0002 + .0005 fee instead of .0000001 + .0005 fee to losers, wallets of gamblers would not cost more to empty than their balance. |
|
|
|
Yes, if I can do them in a laser machine and not have to put a sticker on them, I can crank out thousands of them in a single morning. I can write software to run the laser... and make it so I lay out 150 coins flat, hit start, and it engraves them all with unique private keys in a single batch over the course of several minutes, as well as issuing a script so I can batch-fund them. If I sell the whole thing as a single pack and don't have to deal with stickering or data-entering each coin, the price can come way down.
This technique could be combined with a laser window hologram to restore some security to a circulating coin (although an xray or other electromagnetic imaging could reveal the privkey (note, even laser toner could fall to the dedicated observer, though)). Laser both the public and private on the blank side, and position the window to reveal the public string. You could roll your own "gift" coin, if you are a betting man. Give them a two year expiration date and recall them yourself, in exchange for selling at face value or barely more. Coins may be fun to give out as gifts or promotions, but you never know if they are being circulated, stored, or found their way to the dust bin. On a previous comment, I don't know that even a 0.1 BTC coin should look cheap, it's worth 4.5 x more than a US dollar coin. |
|
|
|
ok thanks so much for the getting-started, once i got going it was quite easy!
I am now running a windows client that:
- gets mail out of a pop box
- gets the senders email and btc address
- send 0.001 btc to the sender
- sends the sender an email.
If anyone's interested how i did it, just let me know!
Thanks again!
Roland.
I'm more interested in sending some emails to this email address! |
|
|
|
|
Show Posts
