Tobin Harding [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2022-04-05 to 2022-07-10
💬 Posted a total of 3 messages
📚 Participated in the following categories: bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-08-12 09:56:44

- reply

📅 Original date posted:2023-08-11
🗒️ Summary of this message: The author is asking for clarification on the expected return value of the function `is_segwit()` for a p2tr transaction and if there is an official name for segwit v0.
📝 Original message:
Question for OG bitcoin API designers please.
If you were to see the following function
`is_segwit()`
would you assume it returns `true` or `false` for a p2tr transaction?
Currently we (rust-bitcoin) are being liberal with the use of `v0` but
its a pretty ugly. Is there an official, or widely used, name for segwit v0?
Thanks,
Tobin.

2023-08-12 09:56:44

- reply

2023-06-07 23:11:25

- reply

📅 Original date posted:2022-07-09
📝 Original message:Hi Peter,
Interesting blog post.
On Sat, Jul 09, 2022 at 11:31:26AM -0400, Peter Todd via bitcoin-dev wrote:
> On Sat, Jul 09, 2022 at 08:24:51AM -0700, Eric Voskuil wrote:
> > To clarify, price inflation is not caused by market production. Attributing the observed lack of inflation (eg fee %) to loss is an assumed relation.
>
> My article is a mathematical proof that has nothing to do with observations of
> inflation.
>
> What I did is prove that if there is tail emission/fixed supply, the coin
> supply will converge towards a fixed amount because the coin supply dependant
> rate of coin loss balances out the fixed rate of coin production.
>
> That proof has nothing to do with market dynamics and would happen in any
> system, economic or not, with similar underlying dynamics.
I'm not a mathematician but I think your models assumption that coin
loss is proportional to number of coins misses something, correct me if
I'm wrong but as value of coins goes up is it not reasonable to expect
coin loss to go down as people are more careful (not to mention
improvements in tooling and education).
Is it really possible to model coin loss as exponential decay
considering such things (I'm not being facetious, that is a real
question, like I said I'm not a mathematician)?
Cheers,
Tobin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220710/3ff76efc/attachment-0001.sig>

2023-06-07 23:11:25

- reply

2023-06-07 23:06:58

- reply

📅 Original date posted:2022-04-06
📝 Original message:On Tue, Apr 05, 2022 at 11:21:17PM +0000, Achow101 wrote:
> The seed is encoded as a WIF private key. Decoding as WIF will result in the 32 byte seed that can be used as specified in BIP 32.
Thanks fro the response Andrew, works as you say!
I am totally _not_ surprised that I was unable to work this out, for future
reference is there anything about those 52 characters from which I should have
been able to tell it is a WIF private key? Why is the seed not just the 32 bytes
of seed data?
Thanks for you time,
Tobin.

2023-06-07 23:06:58

- reply

2023-06-07 23:06:57

- reply

📅 Original date posted:2022-04-05
📝 Original message:Hi,
Does anyone have software that successfully parses the extended private key seed
found in the BIP174 test vector? I have been implementing the test vector PSBT
workflow in Rust and have everything working except I can only create the
extended private key from the xpriv, I am unable to use the seed to create it?
BIP174: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#test-vectors
PSBT workflow in BIP174 starting at the line:
"The private keys in the tests below are derived from the following master private key:"
xpriv:
tprv8ZgxMBicQKsPd9TeAdPADNnSyH9SSUUbTVeFszDE23Ki6TBB5nCefAdHkK8Fm3qMQR6sHwA56zqRmKmxnHk37JkiFzvncDqoKmPWubu7hDF
seed:
cUkG8i1RFfWGWy5ziR11zJ5V4U4W3viSFCfyJmZnvQaUsd1xuF3T
I've tried decoding it as base64 and as base58.
Thanks in advance,
Tobin.

2023-06-07 23:06:57

- reply