📅 Original date posted:2014-05-12
📝 Original message:A Java implementation of what is called BIPSS in lack of an official number
can be found here:
https://github.com/mycelium-com/wallet/blob/master/public/bitlib/src/main/java/com/mrd/bitlib/crypto/BipSs.java
(passing all test vectors)
Which is based on a GF2^8 implementation here:
https://github.com/mycelium-com/wallet/blob/master/public/bitlib/src/main/java/com/mrd/bitlib/crypto/Gf256.java
I think having 3 encoding formats (long/short/compact) is over engineered,
and basically only makes implementing the standard a pain in the rear. From
a user experience point of view only the long format makes sense, and it is
only a few bytes longer than the short version.
On Mon, May 5, 2014 at 9:36 PM, Nikita Schmidt <
nikita at megiontechnologies.com> wrote:
> A fork of Matt's proposal converted to GF(2^8) is here:
> https://github.com/cetuscetus/btctool/blob/bip/bip-xxxx.mediawiki
>
> Other changes include:
> - only six application/version bytes are allocated, which is the
> minimum to ensure that the encoded form starts with S in all cases;
> - encoded prefixes are SK/SL for a shared private key
> (mainnet/testnet) and SS/ST for a shared BIP32 seed;
> - the only hash function in use is SHA-256, which is the all-purpose
> hash function in the Bitcoin protocol;
> - double SHA is used for similarity with Bitcoin, although Jan and I
> believe single SHA is enough in this application;
> - bias-less encoding of M and x, because there can't be more than 255
> shares over GF(2^8).
>
>
> On 23 April 2014 09:16, Gregory Maxwell <gmaxwell at gmail.com> wrote:
> > On Tue, Apr 22, 2014 at 10:33 PM, Tamas Blummer <tamas at bitsofproof.com>
> wrote:
> >> So you agree, that SSS should not contain specific flag for testnet?
> >>
> >> Or for that matter not even BIP32 needs them since it is not an address
> to
> >> send to.
> >
> > I think the convention we have so far is that addresses and address
> > relate thing we share normally contain an opaque 'version' identifier
> > which we use to identify the purpose for the data (E.g. network
> > meaning, etc.) and I think its a generally reasonable custom.
> >
> >
> ------------------------------------------------------------------------------
> > Start Your Social Network Today - Download eXo Platform
> > Build your Enterprise Intranet with eXo Platform Software
> > Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> > Get Started Now And Turn Your Intranet Into A Collaboration Platform
> > http://p.sf.net/sfu/ExoPlatform
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140512/27fd18ec/attachment.html>;
Jan Møller [ARCHIVE] /
npub1sv…jg7a4
2023-06-07 15:21:01
in reply to nevent1q…l7cr
Author Public Key
npub1sv4psc5psjztuewa8xzcxrdsm743zl3lvje7ha36xp3da86hmpyqdjg7a4Published at
2023-06-07 15:21:01Event JSON
{
"id": "1661b58aa2f14e0c8b7b15bb75fdffc0a2645d693c6ecb8b188f509b6267d3cd",
"pubkey": "832a1862818484be65dd3985830db0dfab117e3f64b3ebf63a3062de9f57d848",
"created_at": 1686151261,
"kind": 1,
"tags": [
[
"e",
"3eefbced3b69c9fb63cbaeafb57a99ba7ac481ba4f75a9452433d16927800a47",
"",
"root"
],
[
"e",
"615c979ec62e6b2b1944f205461b952c4cc6f9bb35c78bb1659ef509966b8be7",
"",
"reply"
],
[
"p",
"ee72be6617b6118354dee0b3e02f3d01e8d2b6b83d8437181b3014394ff468f7"
]
],
"content": "📅 Original date posted:2014-05-12\n📝 Original message:A Java implementation of what is called BIPSS in lack of an official number\ncan be found here:\nhttps://github.com/mycelium-com/wallet/blob/master/public/bitlib/src/main/java/com/mrd/bitlib/crypto/BipSs.java\n(passing all test vectors)\n\nWhich is based on a GF2^8 implementation here:\nhttps://github.com/mycelium-com/wallet/blob/master/public/bitlib/src/main/java/com/mrd/bitlib/crypto/Gf256.java\n\nI think having 3 encoding formats (long/short/compact) is over engineered,\nand basically only makes implementing the standard a pain in the rear. From\na user experience point of view only the long format makes sense, and it is\nonly a few bytes longer than the short version.\n\n\n\n\nOn Mon, May 5, 2014 at 9:36 PM, Nikita Schmidt \u003c\nnikita at megiontechnologies.com\u003e wrote:\n\n\u003e A fork of Matt's proposal converted to GF(2^8) is here:\n\u003e https://github.com/cetuscetus/btctool/blob/bip/bip-xxxx.mediawiki\n\u003e\n\u003e Other changes include:\n\u003e - only six application/version bytes are allocated, which is the\n\u003e minimum to ensure that the encoded form starts with S in all cases;\n\u003e - encoded prefixes are SK/SL for a shared private key\n\u003e (mainnet/testnet) and SS/ST for a shared BIP32 seed;\n\u003e - the only hash function in use is SHA-256, which is the all-purpose\n\u003e hash function in the Bitcoin protocol;\n\u003e - double SHA is used for similarity with Bitcoin, although Jan and I\n\u003e believe single SHA is enough in this application;\n\u003e - bias-less encoding of M and x, because there can't be more than 255\n\u003e shares over GF(2^8).\n\u003e\n\u003e\n\u003e On 23 April 2014 09:16, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e wrote:\n\u003e \u003e On Tue, Apr 22, 2014 at 10:33 PM, Tamas Blummer \u003ctamas at bitsofproof.com\u003e\n\u003e wrote:\n\u003e \u003e\u003e So you agree, that SSS should not contain specific flag for testnet?\n\u003e \u003e\u003e\n\u003e \u003e\u003e Or for that matter not even BIP32 needs them since it is not an address\n\u003e to\n\u003e \u003e\u003e send to.\n\u003e \u003e\n\u003e \u003e I think the convention we have so far is that addresses and address\n\u003e \u003e relate thing we share normally contain an opaque 'version' identifier\n\u003e \u003e which we use to identify the purpose for the data (E.g. network\n\u003e \u003e meaning, etc.) and I think its a generally reasonable custom.\n\u003e \u003e\n\u003e \u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \u003e Start Your Social Network Today - Download eXo Platform\n\u003e \u003e Build your Enterprise Intranet with eXo Platform Software\n\u003e \u003e Java Based Open Source Intranet - Social, Extensible, Cloud Ready\n\u003e \u003e Get Started Now And Turn Your Intranet Into A Collaboration Platform\n\u003e \u003e http://p.sf.net/sfu/ExoPlatform\n\u003e \u003e _______________________________________________\n\u003e \u003e Bitcoin-development mailing list\n\u003e \u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Is your legacy SCM system holding you back? Join Perforce May 7 to find\n\u003e out:\n\u003e \u0026#149; 3 signs your SCM is hindering your productivity\n\u003e \u0026#149; Requirements for releasing software faster\n\u003e \u0026#149; Expert tips and advice for migrating your SCM now\n\u003e http://p.sf.net/sfu/perforce\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140512/27fd18ec/attachment.html\u003e",
"sig": "2f28c8528c5ab8618814c23a8c9129bf5600c03653798b8310a0b8c7d501c5bc4cf445c0c1d97732afa89e2b80bcb2ebaa35e059656fdc6585f96adf79485b44"
}