FIXMEs on 3.2 being long winded
This commit is contained in:
parent
247e795904
commit
cf15aaae18
@ -399,11 +399,15 @@ who is performing the authentication to authorize the withdrawal.
|
||||
Preventing the owner of the reserve from deliberately authorizing
|
||||
someone else to withdraw electronic coins would require extreme
|
||||
measures, including preventing them from communicating with anyone but
|
||||
the exchange terminal during withdrawal. As such measures would be
|
||||
the exchange terminal during withdrawal.
|
||||
% FIXME: Oddly phrased:
|
||||
As such measures would be
|
||||
totally impractical for a minor loophole, we are not concerned with
|
||||
enabling the state to strongly identify the recipient of coins
|
||||
from a withdrawal operation.
|
||||
|
||||
% FIXME: Seems to kinda duplicate the previous paragraph, albeit doing
|
||||
% a better job.
|
||||
We view ownership of a coin's private key as a ``capability'' to spend
|
||||
the funds. A taxable transaction occurs when a merchant entity gains
|
||||
control over the funds while at the same time a customer entity looses
|
||||
|
Loading…
Reference in New Issue
Block a user