Raw transaction - forgot to include tx costs - now money in limbo - page 2.

jl2012

legendary

Activity: 1792

Merit: 1111

Quote from: doolittle on January 22, 2014, 12:08:10 AM

By the way, it is this transaction.
b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c

I do not understand why there is a problem.
In the wiki it says.
A transaction may be safely sent without fees if these conditions are met:

It is smaller than 10,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough (see the Technical Info section below)

All the criteria are met.

No, the priority is very very low

Altoidnerd

sr. member

Activity: 406

Merit: 251

http://altoidnerd.com

Quote from: doolittle on January 22, 2014, 12:08:10 AM

By the way, it is this transaction.
b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c

I do not understand why there is a problem.
In the wiki it says.
A transaction may be safely sent without fees if these conditions are met:

It is smaller than 10,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough (see the Technical Info section below)

All the criteria are met.

It will eventually be included in a block. You can see its cue position by searching for the txid b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c
at blockchain.info.

https://blockchain.info/tx/b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c

e4xit

sr. member

Activity: 302

Merit: 250

http://bitcoinfees.com/

This site will explain fees to you a bit better. Some info may be slightly outdated and also Bitcoin-QT 0.9 when released will throw it right off, but you will get a better general understanding.

empoweoqwj

hero member

Activity: 518

Merit: 500

Quote from: doolittle on January 22, 2014, 12:08:10 AM

By the way, it is this transaction.
b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c

I do not understand why there is a problem.
In the wiki it says.
A transaction may be safely sent without fees if these conditions are met:

It is smaller than 10,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough (see the Technical Info section below)

All the criteria are met.

But it doesn't tell you when it will arrive does it ....

empoweoqwj

hero member

Activity: 518

Merit: 500

Quote from: doolittle on January 22, 2014, 12:01:30 AM

Quote from: gweedo on January 21, 2014, 09:32:01 PM

Quote from: doolittle on January 21, 2014, 09:28:56 PM

The thing is, I thought sending 0.05 BTC would be such a large amount that I do not have to spend Tx fees.
But it seems that not only spending but also sending to a multi-sig wallet increases the transaction size and makes tx fees necessary. Sad

Why are you trying to get out of paying fees? Do you believe miners should not be compensated for the time and cpu to verify and find blocks to include your transaction?

Raw transactions can really screw up your bitcoins if you have no clue what you are doing. You can try to recover the tx by doing -reindex on startup of the bitcoin-qt. You should have done this in the testnet where it is safe you can experiment I use the testnet all the time!

to be honest I dislike the fees because I like round numbers. Just aestetics you know. Maybe stupid, but I am sure a lot of people feel this way. Also it is always annoying to count the decimal points to make sure I am sending not too much but also not too few coins. The old discussion about mBTC vs. BTC.

"I dislike fees because I like round numbers" That's one of the weirdest statements I've ever read on this forum Grin

doolittle

full member

Activity: 340

Merit: 101

By the way, it is this transaction.
b4f02e34a2c5349930f92474e57a83670dec05b497ba08c09f982f511a96ab9c

I do not understand why there is a problem.
In the wiki it says.
A transaction may be safely sent without fees if these conditions are met:

It is smaller than 10,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough (see the Technical Info section below)

All the criteria are met.

doolittle

full member

Activity: 340

Merit: 101

Quote from: gweedo on January 21, 2014, 09:32:01 PM

Quote from: doolittle on January 21, 2014, 09:28:56 PM

The thing is, I thought sending 0.05 BTC would be such a large amount that I do not have to spend Tx fees.
But it seems that not only spending but also sending to a multi-sig wallet increases the transaction size and makes tx fees necessary. Sad

Why are you trying to get out of paying fees? Do you believe miners should not be compensated for the time and cpu to verify and find blocks to include your transaction?

Raw transactions can really screw up your bitcoins if you have no clue what you are doing. You can try to recover the tx by doing -reindex on startup of the bitcoin-qt. You should have done this in the testnet where it is safe you can experiment I use the testnet all the time!

to be honest I dislike the fees because I like round numbers. Just aestetics you know. Maybe stupid, but I am sure a lot of people feel this way. Also it is always annoying to count the decimal points to make sure I am sending not too much but also not too few coins. The old discussion about mBTC vs. BTC.

empoweoqwj

hero member

Activity: 518

Merit: 500

Quote from: doolittle on January 21, 2014, 09:14:22 PM

Hi all,
I was redoing the multisig-transaction example of Gavin Andresen.
https://gist.github.com/gavinandresen/3966071/raw/1f6cfa4208bc82ee5039876b4f065a705ce64df7/TwoOfThree.sh
I did not include any transaction costs when I entered the commands which define the "funding"-transaction, i.e. the transaction that "loads" the multi-signature address. Yet sendrawtransaction went through. I created, signed and sent the transaction hours ago (there was a complete: true)
Now my money is somehow in the limbo. My QTwallet tells me that the BTC have left, but since the transaction is unconfirmed the BTC have not entered the multisig-address yet. Do you think that the money will still arrive? Or is it lost?
It is "just" BTC 0.05. No drama, but still pretty annoying.

its a bit early to panic about the coinage disappearing - give it some time. Its only been a few hours right?

gweedo

legendary

Activity: 1498

Merit: 1000

Quote from: doolittle on January 21, 2014, 09:28:56 PM

The thing is, I thought sending 0.05 BTC would be such a large amount that I do not have to spend Tx fees.
But it seems that not only spending but also sending to a multi-sig wallet increases the transaction size and makes tx fees necessary. Sad

Why are you trying to get out of paying fees? Do you believe miners should not be compensated for the time and cpu to verify and find blocks to include your transaction?

Raw transactions can really screw up your bitcoins if you have no clue what you are doing. You can try to recover the tx by doing -reindex on startup of the bitcoin-qt. You should have done this in the testnet where it is safe you can experiment I use the testnet all the time!

doolittle

full member

Activity: 340

Merit: 101

The thing is, I thought sending 0.05 BTC would be such a large amount that I do not have to spend Tx fees.
But it seems that not only spending but also sending to a multi-sig wallet increases the transaction size and makes tx fees necessary. Sad

doolittle

full member

Activity: 340

Merit: 101

Hi all,
I was redoing the multisig-transaction example of Gavin Andresen.
https://gist.github.com/gavinandresen/3966071/raw/1f6cfa4208bc82ee5039876b4f065a705ce64df7/TwoOfThree.sh
I did not include any transaction costs when I entered the commands which define the "funding"-transaction, i.e. the transaction that "loads" the multi-signature address. Yet sendrawtransaction went through. I created, signed and sent the transaction hours ago (there was a complete: true)
Now my money is somehow in the limbo. My QTwallet tells me that the BTC have left, but since the transaction is unconfirmed the BTC have not entered the multisig-address yet. Do you think that the money will still arrive? Or is it lost?
It is "just" BTC 0.05. No drama, but still pretty annoying.

Topic: Raw transaction - forgot to include tx costs - now money in limbo - page 2. (Read 2141 times)