openmoney specifications

openair (Hackpad import)

Visible to members of this folder

open money is an aspect of free speech - it is a context

see REA

open money can be called free money

as in free speech, not as in free beer / lunch / load / ride

openmoney is a project enabling open money, operating in accordance with the principles and intellectual properties of the LETSystem Trust

openmoney is freely available on line

a registered steward of openmoney can be any person or organization of persons that recognizes that they are responsible for their :

accounting of events

fulfilment of promises

to use open money is to mind your own business

A steward has a stewardname, and a public key.

A steward may optionally provide an email and choose their notification settings.

A steward uses their stewardname and private key to authenticate themselves.

A stewards public and private key can be deterministically generated using their stewardname and password.

When a steward registers they are given a private namespace with the namespace name:stewardname and with the parent namespace:cc

every namespace can also be a currency or accounting set with the steward of the namespace

currency parameters are declared by steward

access terms are set by steward

A namespace has a namespace name, parent namespace and a (set of) steward(s)

A namespace is globally unique

Namespace stewards get notified when stewards create a child namespace, currency or account.

Namespace stewards have the ability to enable or disable child namespaces, currencies, or accounts.

Namespace stewards have the ability to move child namespaces, currencies or accounts from their namespace to another.

Namespaces can be public or private, a public namespace means when a child namespace, currency or account is created it its automatically enabled, and private is automatically disabled.

A currency has a currency name, parent namespace, and a set of zero or more stewards.

Currency stewards get notified when stewards create an account that uses this currency.

Currency stewards have the ability to enable or disable accounts used by this currency.

Currency stewards get a copy of all journal entries that use the currency..

Currency stewards have the ability to void journal entries by posting a reversing journal entry on behalf of both parties.

Currencies can be public or private, a public currency means that when an account is created that uses this currency it is automatically enabled, and private is automatically disabled.

An account has an account name, account parent namespace, currency, currency parent namespace and a set of stewards.

Account stewards post journal entries from one account to another account in the same currency.

A Journal has a to account name, to account namespace, from account name, from account namespace, currency name, currency namespace and amount.

A Journal entry is sent to the server. The namespaces, currencies and accounts are verified that they are enabled. If they are enabled the journal entry is encrypted using the to account stewards, from account stewards and currency stewards public keys, the encrypted journal entry is stored on the server for their retrieval and the stewards are notified.

The response is an, ok successful or an error based on the verification of the enabled state of the accounts, currencies and namespaces.

List journal entries for a given account. Returns a list of journal entries to or from that account.

notes from https://tools.ietf.org/html/rfc7519

Collision-Resistant Name

A name in a namespace that enables names to be allocated in a

manner such that they are highly unlikely to collide with other

names. Examples of collision-resistant namespaces include: Domain

Names, Object Identifiers (OIDs) as defined in the ITU-T X.660 and

X.670 Recommendation series, and Universally Unique IDentifiers

(UUIDs) [RFC4122]. When using an administratively delegated

namespace, the definer of a name needs to take reasonable

precautions to ensure they are in control of the portion of the

namespace they use to define the name.

John Waters 5 years ago

Perhaps this statement should be clarified.

John Waters 5 years ago

Yes, I get that. I was wondering why “openmoney” is lower case when the use of

John Waters 5 years ago

Is term “promises” intended to mean something more than “commitments”?

John Waters 5 years ago

Thanks.

John Waters 5 years ago (edited)

At this time, the openmoney-network interface allows the steward to log in only

John Waters 5 years ago

My point was that (in contrast to this specification) stewards currently log in

John Waters 5 years ago

Again, this is currently done using username and password.

Michael Linton 5 years ago

right

John Waters 5 years ago

I assume this is what’s done at present since upon registration of a new steward

John Waters 5 years ago

DL confirmed/explained this in his email earlier today.

John Waters 5 years ago

Why is a namespace globally unique?

John Waters 5 years ago

John Waters 5 years ago (edited)

Does this mean that the steward of a particular namespace is notified when anoth

John Waters 5 years ago

OK. That helps.

John Waters 5 years ago

How does a steward know which other stewards and namespaces exist? How does a st

John Waters 5 years ago

If namespaces were not globally unique, that would not necessarily cause a probl

John Waters 5 years ago

OK. That’s not at all clear from this specification.

John Waters 5 years ago

How does the steward (A) of the child (namespace, currency or account) request p

John Waters 5 years ago

OK, but I’m sure something more sophisticated can be worked out down the line.

John Waters 5 years ago

What can be done within a private namespace?

John Waters 5 years ago

Should that read something more like “All stewards of a currency get notified wh

John Waters 5 years ago

That’s reassuring. (I often get confused by others’ sentence constructions so h

John Waters 5 years ago

To disable all accounts using that currency, regardless of ownership?

John Waters 5 years ago

OK, that’s what I would have expected.

John Waters 5 years ago

Should that be something like “All stewards of a currency get a copy of all jour

John Waters 5 years ago

What can be done with a private currency? Is this simply a temporary state whil

John Waters 5 years ago

OK, that makes it much clearer. Thanks.

John Waters 5 years ago

I assume this “set of stewards” includes all stewards with the ability to make a

John Waters 5 years ago

OK. Again this may need to be reworded slightly.

John Waters 5 years ago

… I assume the “account steward” is the steward with administrative/control privileges for the account as distinct from stewards able to make payments using this currency.

Michael Linton 5 years ago

the stewards here are only those permitted to use this name

John Waters 5 years ago

That’s less clear. I’ll scratch my a head while and get back to you.

Michael Linton 5 years ago

an account name can have many stewards

a currency will have multiple account names, each with its own steward(s)

the essence of this statement is perhaps that accounts MUST be using the same currency to post

John Waters 5 years ago

That’s what I assumed.

[The reasons why I’m trying get all this absolutely clear to me are that (a) I want to be able to explain it to others (possibly using set notation - which is what I started doing a few days ago) and (b) because I want my Python code to be compatible functionally (but with a superset of functions).]

John Waters 5 years ago

(This brings me back to the question of why the CSV export doesn’t include all o

John Waters 5 years ago

OK. I think a slower cobble would be a lot more useful.

John Waters 5 years ago

I assume this means that three copies of the journal entry are saved, each in a

Michael Linton 5 years ago

currency steward can only see what accounts are doing in that currency - not the