I got several feedback and questions in private, some excerpt:
[Q about my other related papers]
surprisingly few written words (on this subject) by me. I've been
studying the moneypulation and money problems for quite a while,
only a few EN words (on my otherwise Hungarian site):
http://www.falura.hu/en/
note: I have no illusions about political/parliamental solutions.
My answer on a loom.cc developer's mail:
I think we should stir public discussion on this, involving
ripplepay.com and loom.cc and other openmoney, communitycurrency and
reinventingmoney developers.
Actually, I'm convinced we need to use some wiki, because on a forum
we cannot polish ideas and system specs
in short, the whole system boils down to 3 parts:
* 1) Digital Coin
http://anchk.250free.com/ Focus on the base
concept, the redemption curve. It is marvellous (+lotsof garnish not
necessary to understand the concept, some examples are actually
incorrect)
* 2) auditable currency issuance and accounting (allowing anonymous
"swissbank" accounts)
* 3) "market providers" that consider the pricelists of market
recipients and find best path to make currencies "convertible"
At this time (I've spent quite some time thinking about this) I think
1)-2) are quite easy and scale easily.
The hard part is 3), but it's getting clear to me how it will work and
which teams are close to design and implement it.
Also, how it will spread, first by utilizing the high fees and latency
of international transfer of fraud-money.
> Correction: loom.cc *does* allow verification of issued amount.
> For example, here is the current issuance of an asset type:
>
https://loom.cc/?function=grid&action=look&type=26ef701a952fe3d641a69bf859d
>b71c2&hash=50025bea374c44337c6ef28d8d9a44be1af386f4e571981a1521e88188d72499
> You can see the current value of -
2177243377, which is the current
> liability of the issuer in integer units
(217.7243376 grams of gold)
>
https://loom.cc/?function=help&topic=grid_tutorial
By auditing the money supply, I mean that "for each token someone can
use to pay with, anyone can verify it is part of the known amount of
issued money".
The loom.cc "look" operation is not real auditing. It's trivial to use
a server that outputs -
2177243377 for a similar query (== fractional
reserve banking).
As I said, 3) seems to be more work than 2). (That's why much hope is
in ripple developers who are likely to play an important role here)
Also, because of complexity, it seems to me we need do 3) in Java
first. When the APIs and reference implementation exists, it is
possible to implement in other (more "host-friendly") language(s) such
as C++ or even PHP / Perl if we want to make it possible for a larger
part of the opensource community to play with the concept.
Marcell
----
I just talked to a lawyer. He confirmed that it's legal for someone to
sign a contract which explicitely states that he can pass on his right
(eg. to access a service) to someone else based on electronic codes.
So good contract text (==signed digital coin) is just a matter of
wording. The enduser's agent (purse software) will need to implement
some considerations (when preparing transactions). Besides
individually determined preferences, the purse considers the
redemption curve and market value of currencies to decide which one to
trade.