š
Original date posted:2014-10-01
š Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 1 October 2014 11:23:55 GMT-07:00, Luke Dashjr <luke at dashjr.org> wrote:
>Thoughts on some way to have the stack item be incremented by the
>height at
>which the scriptPubKey was in a block?
Better to create a GET-TXIN-BLOCK-(TIME/HEIGHT)-EQUALVERIFY operator. scriptPubKey would be:
GET-TXIN-BLOCKHEIGHT-EQUALVERIFY
(fails unless top stack item is equal to the txin block height)
<delta height> ADD
(top stack item is now txin height + delta height)
CHECKLOCKTIMEVERIFY
> A limitation of encoding the
>target
>height/time directly, is that miners may choose not to mine the first
>transaction until they can also take the "burn to fee". So, one may
>prefer to
>say "cannot be spent until 100 blocks after the first transaction is
>mined",
>in effect reproducing the generation maturity rule.
You'd want these sacrifices to unlock years into the future to thoroughly exceed any reasonable business cycle; that's so far into the future that miners are almost certain to just mine them and collect the fees.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCAA6BQJULJa7MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhYlFB/4r2Hv82RK85BDe+hAT
ZQJtzXv1JRCa+o7Y344unMJ8y7rSDJRFSH+X+4VeCln833XKb8FNgj2loniQAq5H
FIH04gPf7yuXvDrKI6HwCj9Q3KLPv4UZM1+LjijczOM/y4e/C82squpTpgFaton+
6VXU/WyaCDYDS4he975E14YhBBVhoadZZMOW3Moxgpnde2RwAYZdkcdhqvh/3dJC
/9VOEUBu0ENyraL5HHGdZyjSJT2MsY4CBTCCd54RxBBMoMZqFRvIi4Xrt2vE1T+Y
R2DtKs7upjydnfg9KPm484upvO2U3lcnPBW9rqOVQyV2q81TcloRtUIU4QQ9GCAk
ayj2
=p0BG
-----END PGP SIGNATURE-----
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 15:26:06
in reply to nevent1qā¦0fsd
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 15:26:06Event JSON
{
"id": "f134c9c4112e1b98269c21ac8b09ebe274d8642c74d500e2eea62c9c21c31f40",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686151566,
"kind": 1,
"tags": [
[
"e",
"b0d4dbe43a898155b6750ed1dce6a700ce007fe7f2dce49b1bbfe7e2cca60c4c",
"",
"root"
],
[
"e",
"1d7f366538d6525e1c20244e5eb9c7dd6c928d32cb7f9f4a030410b7e8546667",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "š
Original date posted:2014-10-01\nš Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n\n\nOn 1 October 2014 11:23:55 GMT-07:00, Luke Dashjr \u003cluke at dashjr.org\u003e wrote:\n\u003eThoughts on some way to have the stack item be incremented by the\n\u003eheight at\n\u003ewhich the scriptPubKey was in a block?\n\nBetter to create a GET-TXIN-BLOCK-(TIME/HEIGHT)-EQUALVERIFY operator. scriptPubKey would be:\n\n GET-TXIN-BLOCKHEIGHT-EQUALVERIFY\n\n(fails unless top stack item is equal to the txin block height)\n\n \u003cdelta height\u003e ADD\n\n(top stack item is now txin height + delta height)\n\n CHECKLOCKTIMEVERIFY\n\n\u003e A limitation of encoding the\n\u003etarget\n\u003eheight/time directly, is that miners may choose not to mine the first\n\u003etransaction until they can also take the \"burn to fee\". So, one may\n\u003eprefer to\n\u003esay \"cannot be spent until 100 blocks after the first transaction is\n\u003emined\",\n\u003ein effect reproducing the generation maturity rule.\n\nYou'd want these sacrifices to unlock years into the future to thoroughly exceed any reasonable business cycle; that's so far into the future that miners are almost certain to just mine them and collect the fees.\n-----BEGIN PGP SIGNATURE-----\nVersion: APG v1.1.1\n\niQFQBAEBCAA6BQJULJa7MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8\ncGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhYlFB/4r2Hv82RK85BDe+hAT\nZQJtzXv1JRCa+o7Y344unMJ8y7rSDJRFSH+X+4VeCln833XKb8FNgj2loniQAq5H\nFIH04gPf7yuXvDrKI6HwCj9Q3KLPv4UZM1+LjijczOM/y4e/C82squpTpgFaton+\n6VXU/WyaCDYDS4he975E14YhBBVhoadZZMOW3Moxgpnde2RwAYZdkcdhqvh/3dJC\n/9VOEUBu0ENyraL5HHGdZyjSJT2MsY4CBTCCd54RxBBMoMZqFRvIi4Xrt2vE1T+Y\nR2DtKs7upjydnfg9KPm484upvO2U3lcnPBW9rqOVQyV2q81TcloRtUIU4QQ9GCAk\nayj2\n=p0BG\n-----END PGP SIGNATURE-----",
"sig": "138fd6b1806682bdc1b080b8fe2e1a74f66b94b029fe218fbbac17e4da1c991db68c529bab87585a04653b3819e79f52a959eadb6e0508f5078ad1c93f3264f4"
}