lokad/terab

Discontinued, replaced by CashDB

terab's Issues

Clarify why the Bitcoin address is required as part of `protocols.csv`

The intent behind Bitcoin addresses in protocols.csv is not entirely clear and should be clarified (hint: it's to sort out conflicting claims that may arise later on).

Protocol Identifier: Cash Accounts

Requesting the 0x 01010101 identifier for the Cash Accounts protocol.

A display name for the protocol: Cash Accounts
An author (or list of authors): Jonathan Silverblood
A URL pointing to the specification of the protocol: https://gitlab.com/cash-accounts/specification (not yet published)

Little endian or big endian?

Some protocols are using little endian in the list, others are using big endian. Example:
(SLP) https://trends.cash/#/result/cHJlZml4OiA1MzRjNTAwMA==/90
(Bookchain) https://trends.cash/#/result/cHJlZml4OjAwMDBCMDA2/90
What is the correct way?
Also, the list should use only little OR big endian, not both.

Protocol identifier for stealth addresses

I'm gonna just go ahead and suggest the following OP_RETURN prefix for stealth address payments ( https://www.youtube.com/watch?v=43K_z0sWtEU )

0x0057ea178

looks sort of like "STealTH" to my leet-speek conditioned eyes. :D

Guideline for protocol identifiers, clarify endian-ness

The endian-ness of values presented in the guideline must be clarified.

Clarify the status of the 0x04 in the guideline

The guideline on protocol identifier prefixes, the role of the 0x04 should be clarified. Otherwise people may end-up ignoring and/or misunderstanding this part of the guideline.

Adding RedirectUrl column to protocols.csv

It will not be possible for the blockchain explorers to implement all of these protocols, but they could automatically generate a redirect button to redirect to the protocol's main site including the TXN id within the URL. The redirected site can then display the desired experience of the protocol.

Maybe this was already one intent of all of this, so I'm just saying a TxnRedirectUrl column maybe should be added with a common placeholder that can be replaced programmatically by a blockchain explorer (e.g., simpleledger.cash/txn/{txn_id} where `{txn_id} would be automatically replaced).

Reserve 0-1024 ids for trustless/decentralized replacements

I suggest to reserve 0-1024 ids for TCP/IP services with their corresponding trustless/decentralized replacements in future. For example, id 53 could be for trustless/decentralized DNS service of the future.