Support Stampery

[aesedepece]

Hi,

It would be great if Stampery's OP_RETURNs could appear correctly tagged in http://opreturn.org/

We are currently using prefix S4 (5334 in hex), although we also used S1, S2 and S3 in the past.

Thanks for your attention and congratulations for this project and for Eternity Wall as well.

Best,

[RCasatta]

I see there are a lot of S1 tx lately. Are them always from Stampery?

[RCasatta]

I added 53311b for now 942a0b8
Actually it's working considering the first three bytes, some grouping it's considered but never all cases after the first two bytes...

private void initMaps() {
        map.put("BIT", "Bitproof");
        map.put("DOC", "Docproof");
        map.put("FAC", "Factom");  //464143
        map.put("SPK", "Coinspark");
        map.put(new String(fromHex("4f4101")) , "Open Assets");
        map.put(new String(fromHex("434301")) , "Colu");
        map.put("ASC", "Ascribe pool");
        map.put("EW ", "Eternity Wall");  //455720
        map.put(new String(fromHex("4d4700")), "Monegraph");
        map.put("id;", "Blockstack");  //69643b
        map.put("CNT", "Counterparty");
        map.put("omn", "Omni Layer");
        map.put(new String(fromHex("53311b")) , "Stampery");

        hexGrouping.put("4d47ff", "4d4700");  // MG? -> MG?
        hexGrouping.put("455741", "455720");  // EWA -> EW
        hexGrouping.put("455743", "455720");  // EWC -> EW
        hexGrouping.put("466100", "464143");  // Fa? -> FAC
        hexGrouping.put("69642b", "69643b");  // id+ -> id;
        hexGrouping.put("69643a", "69643b");  // id: -> id;
        hexGrouping.put("69643f", "69643b");  // id? -> id;
        hexGrouping.put("69643e", "69643b");  // id> -> id;
    }

[aesedepece]

Funnily enough, we stopped using S1 nearly one year ago and those starting with S1 lately are not ours. So someone seems to be using our old prefix 😆

We are currently using only S4 to identify transactions made by version 4 of our platform.

[RCasatta]

removed S1 mapping to Stampery and added a grouping for S4 following any byte.
Still not sure to map a protocol with only two bytes but anyway will see how it goes.

[aesedepece]

Thanks a lot!

Our CTO at Stampery started using S1 when he started the project on his own and up to now we have only continued with the "tradition" of changing the second byte every time we made a major upgrade to our blockchain data anchoring technology.

But it is something that has not been properly discussed or sufficiently reasoned. As far as I know there are no written rules on prefix length, but in view of what other players in the bitcoin community are using, I wonder if we should abide to the apparent consensus and embrace a three bytes prefix.

@RCasatta What do you reckon? I would love to hear some feedback!

[RCasatta]

There are absolutely no written rules on prefix length, neither they could never be imposed! Luckily we are still permissionless and censorship resistant :)
That said, I personally would prefer protocol discrimination with two bytes and the third for internal version or type. I think it's a good compromise between space usage and collisions avoidance.

[aesedepece]

FYI: Stampery has just started to use S5 😸

[aesedepece]

FYI: Last January, Stampery started using the S6 tag and deprecated all former versions. Shall I PR?

[RCasatta]

I am sorry but at the moment the site is not well maintained (data looks stuck June) and I didn't look at the problem yet