Try   HackMD

Discuss with Lewis Freiberg in NCKU (2017-11-25)

New features

  • MAM
  • Asymmetric Symmetric/Encryption
  • usage of security in mam::create
  • Transaction agent
  • Group identity
  • To identify a group, company or organization
  • Private key lost recovery
  • One or two guarantor when create a new identity
  • When a identity lost key or device
    1. The identity register a new account
    2. Then notify his guarantor
    3. Guarantor can sign a key special lost caim for the identity
    4. Finally tangleID will send a special calim from APP to every claim issuer for requesting to re-sent a new claim to the new identity
  • Revoke claim
  • revoke a claim - API
  • Colored coin - API
  • A special UUID type with value

Integrated Use Cases


Discussion

  • Colored coin
curl http://HOST_URL \
-X POST \
-H 'Content-Type: application/json' \
-d '{"command":"send_token",uuid": "9JVXCXMFAMKLUQQCDACSWJVDLH","receiver":"9JVXCXMFAMKLUQQCDACSWJVDLH","value":"100","msg":"HELLO"}'
  • Off-tangle data:
    About the off-tangle date, we plan to store in the IPFS or just write content into the Tangle e.g:iota-storage/storage-web, any suggestion ?

  • Conflict transaction:

  • A clear definition about conflict transaction on Tangle?
    • Duplicate transaction hash (possible?)

      Yes.

    • The code section of IRI to handle the conflict transaction ?
      Yes.

    • Can conflict transactions be defined by user? I think it should be.Beacuse different application needs different definition of conflict transactions.
      No.

  • Tangle
  • Does node(IRI) choose the max weight(cumulative weight) transaction in conflict transactions?

    Yes.

  • Does MCMC deal with "lazy tips"? I mean the probability of choosing "lazy tips" is low when use MCMC to choose tip.

    Don't know.

  • Transaction in tangle never be deleted.

    Yes.

    But it will be merged when node snapshots.