jsonrpc "move" history? | Bitcointalksearch.org

payb.tc

hero member

Activity: 812

Merit: 1000

Quote from: theymos on March 13, 2012, 10:41:10 PM

Quote from: dunand on March 13, 2012, 10:14:59 PM

Will I have to pay a higher transaction fee because of that?

No. The accounting entries created by move aren't real Bitcoin transactions.

which is what caused me to assume they weren't recorded as transactions at all, but rather some kind of adjustment that overwrote stuff.

theymos

administrator

Activity: 5222

Merit: 13032

Quote from: dunand on March 13, 2012, 10:14:59 PM

Will I have to pay a higher transaction fee because of that?

No. The accounting entries created by move aren't real Bitcoin transactions.

dunand

hero member

Activity: 637

Merit: 502

If I understand correctly. If I do
move('alice','bob',25);
move('bob','alice',25);
ten thousand times my wallet should grow because of all the transactions? Will I have to pay a higher transaction fee because of that?

payb.tc

hero member

Activity: 812

Merit: 1000

Quote from: theymos on March 13, 2012, 08:03:44 PM

It is recorded. You can see them in listtransactions.

oh thanks... i didn't think the move function had anything to do with transactions.

theymos

administrator

Activity: 5222

Merit: 13032

It is recorded. You can see them in listtransactions.

payb.tc

hero member

Activity: 812

Merit: 1000

i'm wondering if the jsonrpc command 'move' leaves a history behind somewhere or if opposing moves cancel each other out.

eg. if i did this a million times:

move('alice','bob',25);
move('bob','alice',25);

would it cause bloat somewhere? or would each run through the loop cancel out the previous one?

Topic: jsonrpc "move" history? (Read 1240 times)