TRB-I Addressing Scheme Proposal
Sunday, 26 February, Year 9 d.Tr. | Author: Mircea Popescu
Since discussion of the Ideal Bitcoin progressed some in the Republican forum today, and since I can't say I'm a great fan of the current addressing scheme, here's a proposal for an alternative implementation :
A TRB-I address under this scheme would be composed as follows :
- To a one byte versioni is added a 512 byte public key.
- The 513 byte numeral from the previous step is put through MPFHFii, obtaining a numeral of an unspecified length.
- The numeral of unspecified length from the previous step is put through keccakiii, resulting in a 256 bit outputiv.
- A one byte checksum is calculated as the successive xor of the 32 bytes from the previous step and added at the end, resulting in a 33 byte output.
- The 33 byte output from the previous step is put through base64v. The result is a TRB-I address, I guess you can prepend B to it or whatever.
Comments welcome.
———- Version 0 is 4096 bit RSA (as discussed). Other versions may be implemented, up to a total of 255 alternatives. If the implementation uses less than 4096 bits for its public key, it is required to also provide a padding scheme as part of its specification. [↩]
- MP's Fabulous Hash Function. [↩]
- Specifically no NIST "standards" are being contemplated or seriously considered. All those who seriously believe USG crypto may or should be taken seriously are rank imbeciles who can't, nor should, be taken seriously. [↩]
- The keccak implementation will be configured to actually offer 256 security bits ; in any case the number of rounds used will not be less than 64. [↩]
- And let the idiots who run terminals with bad glyphs buy better hardware / run better software. [↩]
Category: Bitcoin
Sunday, 26 February 2017
Did I miss a collision-resistant variant of your hash algo?
Sunday, 26 February 2017
Did a collision get demonstrated and I slept through it ?
Saturday, 4 March 2017
Actually on consideration all trb-i addresses should be in the format B|hash (capital-b-pipe-hash).
Saturday, 4 March 2017
Why break unix shell with that pipe?
Saturday, 4 March 2017
Because it's a piece of shit which broke EVERYTHING we had. EVERYTHING!!! With its bdb and its gcc and its boost and its fuck its mother. That's fucking why.
Sunday, 5 March 2017
The old story (from trilema! incidentally) re: the fella who stomped the samovar, "gotta kill'em while they're small!" -- comes to mind.
Sunday, 5 March 2017
Quite exactly.