Re: [bitcoin-dev] BIP49 Derivation scheme changes

2017-09-05 Thread shiva sitamraju via bitcoin-dev
n-dev@lists.linuxfoundation.org> > Subject: Re: [bitcoin-dev] BIP49 Derivation scheme changes > Message-ID: <9da64df3-c6a9-c232-c801-f379a6d65...@satoshilabs.com> > Content-Type: text/plain; charset=windows-1252 > > On 05/09/17 09:10, shiva sitamraju via bitcoin-dev wrote: >

Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32

2017-09-12 Thread shiva sitamraju via bitcoin-dev
b.com/jl2012/bitcoin/commits/vault > https://github.com/jl2012/bitcoin/commit/f3f201d232d3995db38e09b171e4d1 > dea8d04ad2 > > But this does more than your proposal as it allows users adding extra > scripts when spending a coin. The rationale is described in the revised > BIP114: &

[bitcoin-dev] BIP49 Derivation scheme changes

2017-08-30 Thread shiva sitamraju via bitcoin-dev
Hi, I wanted to discuss few changes in BIP49 *- Breaking backwards compatibility * The BIP talks about breaking this, and but it really doesn't. I really feel it should completely break this. Here is why What would happen if you recover a wallet using seed words ? 1. Since there is no

Re: [bitcoin-dev] BIP49 Derivation scheme changes

2017-09-05 Thread shiva sitamraju via bitcoin-dev
ed to be 4 mb then 40 mb, then what > > is the real limit? Otherwise waiting times and thus the fees will just > > grow rapidly. I don't think that it is desirable. > > The real limit is set by the technology. Just like in 1990 we could not > fathom having something like YouTube and high-

[bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread shiva sitamraju via bitcoin-dev
Hi, When I copy and paste bitcoin address, I double check the first few bytes, to make sure I copied the correct one. This is to make sure some rogue software is not changing the address, or I incorrectly pasted the wrong address. With Bech32 address, its seems like in this department we are

Re: [bitcoin-dev] Visually Differentiable - Bitcoin Addresses

2017-10-30 Thread shiva sitamraju via bitcoin-dev
> sufficient for ensuring that it is correct as it takes less than a second > to generate a 3 character vanity address that matches the first 3 > characters of an address. > > On Mon, 30 Oct 2017, 11:44 shiva sitamraju via bitcoin-dev, < > bitcoin-dev@lists.linuxfoundation.org&g

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-05-30 Thread shiva sitamraju via bitcoin-dev
The idea to add birthdate and gap limit sounds very good and addresses lots of problems users are facing. However, adding birthday to keys breaks two basic properties - Visually Comparing two keys to find if they are same (Important) - Different wallet software could set different birthday/gap

[bitcoin-dev] Testnet3 Reest

2018-08-30 Thread shiva sitamraju via bitcoin-dev
Hi, Testnet is now 1411795 blocks and a full sync is taking atleast 48 hours. Is a testnet reset scheduled in the next release or any reason not to do a reset ? Fast onboarding/lower disk overheads would be very much appreicated for testing purposes Regards -- Shiva S CEO @ Blockonomics

Re: [bitcoin-dev] URI scheme with optional bech32 address

2018-09-25 Thread shiva sitamraju via bitcoin-dev
Hi, I am not sure why this wasn't discussed more but it seemed like a very good idea to me https://www.reddit.com/r/Bitcoin/comments/9iivej/its_been_like_a_year_and_bech32_adoption_remains/ QR code is very important for network wide adoption. The problem is bech32 qr code isn't backward