juliendonck

➜  radicle-upstream git:(master) yarn
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed in 0s 425ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 439ms
➤ YN0000: Done in 1s 106ms
➜  radicle-upstream git:(master) yarn start
   Compiling api v0.1.0 (/Users/juliendonck/code/radicle-upstream/proxy/api)

juliendonck

# Spoken

We always say `open source coin` and you can use it to describe the team such as `open source coin team`.
Although if that is too long or feels clunky, you can use `oscoin team` to describe a part of open source coin.

When using the abbreviated `oscoin` it should always be in combination with something else, not by itself. And you should pronounce it *'oh-es-coin'*, not *'os-coin'*.

# Written

### DO

juliendonck

{
    address: '',
    contract: {
    },
    funds: {
      oscoin: 0,
      exchanges: [],
    },
    meta: {
    },

juliendonck

Keybase proof

I hereby claim:

• I am juliendonck on github.
• I am juliendonck (https://keybase.io/juliendonck) on keybase.
• I have a public key ASCLXCwA4btfj_rRVKi1EtE3f0XXXtMf9WiVarDaRwOAuwo

To claim this, I am signing this object: