Hello,
I should have brought up this suggestion before, as there seems to be relevant
other work.
I'd like to propose encoding keys data (whatever type) with a birth timestamp
as:
* @
The reason for not incorporating this inside the key serialization (for example
BIP32), is because
birth tim
On 22 July 2013 16:44, Pieter Wuille wrote:
> Hello,
>
> I should have brought up this suggestion before, as there seems to be
> relevant other work.
>
> I'd like to propose encoding keys data (whatever type) with a birth
> timestamp as:
> * @
>
> The reason for not incorporating this inside the
2 matches
Mail list logo