jsonrpc "move" history?

[payb.tc]

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?

[1713907073]

1713907073

[1713907073]

1713907073

[1713907073]

1713907073

[theymos]

It is recorded. You can see them in listtransactions.

[payb.tc]

It is recorded. You can see them in listtransactions.

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

[dunand]

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?

[theymos]

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

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

[payb.tc]

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.