Author

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

hero member
Activity: 812
Merit: 1000
March 14, 2012, 12:30:23 AM
#6
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.
administrator
Activity: 5166
Merit: 12850
March 13, 2012, 11:41:10 PM
#5
Will I have to pay a higher transaction fee because of that?

No. The accounting entries created by move aren't real Bitcoin transactions.
hero member
Activity: 637
Merit: 502
March 13, 2012, 11:14:59 PM
#4
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?
hero member
Activity: 812
Merit: 1000
March 13, 2012, 09:10:18 PM
#3
It is recorded. You can see them in listtransactions.

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

administrator
Activity: 5166
Merit: 12850
March 13, 2012, 09:03:44 PM
#2
It is recorded. You can see them in listtransactions.
hero member
Activity: 812
Merit: 1000
March 13, 2012, 09:01:30 PM
#1
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?
Jump to: