Anthony Towns via bitcoin-dev wrote:
[SNIP]
>
> My thinking at the moment (subject to change!) is:
>
> * anyprevout signatures make the address you're signing for less safe,
>which may cause you to lose funds when additional coins are sent to
>the same address; this can be avoided if han
Mr. Lee Chiffre via bitcoin-dev wrote:
> Right now bitcoin client core supports use of tor hidden service. It
> supports v2 hidden service. I am in progress of creating a new bitcoin
> node which will use v3 hidden service instead of v2. I am looking at
> bitcoin core and btcd to use. Do any of the
ic via bitcoin-dev wrote:
Hi,
On 4 Aug 2021, at 12:30, Justin Valceanu via bitcoin-dev
wrote:
I have created a new Romanian wordlist for Bip-0039;
Requesting permission to push to github the attached modified files.
Although I don’t think it ’s hard requirement, it would be great if the wo
raymo via bitcoin-dev wrote:
TL,DR: you were explained by ZmnSCPxj why this protocol will not work.
The possibility for just one party to sign will not work. I will explain
again why but in much more simpler description.
Check out this simple transaction to learn more about how the system
w
Hi,
I think this would be too complicated in practice and you'd have to
defend against many other types of attacks, including but not limited to
Sybil attacks, misbehaving servers not responding to requests,
misbehaving servers not forwarding requests, you'd need some kind of
directory servers or
We could care less about you selling your bitcoins or moving to
something else.
What we care more is keeping bitcoin a successful project which offers
clear benefits to the world. I agree a fee market is good and needed,
and transactions shouldn't be free ever, but users should also be able
to tra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Interesting point of view Thomas! I agree that if we only think
towards one single direction (treat trust as a super bad thing) we
might miss some good features (or scalability levels) among the way.
Benjamin:
> Lightning assumes explicit trust and
On 8/15/2015 8:02 PM, Mike Hearn via bitcoin-dev wrote:
>
> I say to all developers on this list: if you also feel that Core is no
> longer serving the interests of Bitcoin users, come join us. We don't bite.
>
Bwhahahahahahahhahahahahah
___
bitcoin-de
Fair enough, this is what open source is all about. Good things
sometimes come out of controversial actions. I briefly read the
manifesto, saw the migration plan, it is not that greedy and in theory
it is possible to migrate safely with no (big) incidents.
What seams a little bit unfair is that on
Hello Jorge, Eric,
With all this noise on the -dev mail list I had to implement application
level filters so I can treat with priority posts from certain people,
you are on that list. While I agree with your arguments, I think it is
_very_ important to highlight some things. I am neither for the
b
On 8/20/2015 1:28 AM, Jorge Timón wrote:
[snip]
>> 3. If Bitcoin's value can be decreased (or Bitcoin as a project killed)
>> just by 2 people forking the software and submitting a consensus rule to
>> a vote, it means Bitcoin is dead already and it should be worthless! We
>> can't go around and p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Please stop with the nonsense. Bitcoin is a decentralized payment
network. It operates globally, so neither jurisdiction can apply to it
and have effects. It is the sole responsibility of all the
users/businesses involved in Bitcoin to comply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
2^256 x _NO_
On 8/28/2015 5:00 AM, odinn via bitcoin-dev wrote:
> No.
>
> On 08/27/2015 01:10 AM, prabhat via bitcoin-dev wrote:
>> Hi,
>
>> I am proposing to create a AML-KYC module to control the network
>> and also qualify use cases in OFAC co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Decentralization depends on the context and does not have a definition
in a form that it was demanded... I can confirm we have people in our
community which do understand decentralization, and quite good
actually, just there is no definition if the f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That would be very wrong and cause a lot of problems and 'political
chaos' without solving at least one (technical) problem in exchange.
Bitcoin Core is a good quality code. It is open source and free.
Anyone can contribute and submit small changes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nobody said anything about trusting the governments in the way such as
you describe.
No matter how much you want to disagree here, Mike Hearn is right on
some aspects. He only said that bitcoin needs to have larger user
base, more use cases, making
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1
I was actually waiting for this. It makes 'smart contracts' simpler
and better from many points of view.
Pete I don't see anything about RCLTV in BIP65, was that a separate
BIP? Which one is it and are we also deploying it via
IsSuperMajority()?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi aj,
On 10/4/2015 11:35 AM, Anthony Towns via bitcoin-dev wrote:
> On Sat, Oct 03, 2015 at 04:30:56PM +0200, Peter Todd via
> bitcoin-dev wrote:
>> So we need to make the case for two main things: 1) We have
>> applications that need a relative (i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
First, this only makes reference to hard forks not to soft forks. This
is very important because we are trying to apply a hard fork
requirement to a soft fork procedure which obviously won't work.
Your statement that 'all objections coming f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I am reading about the Lightning Network and the BIPs which need to be
deployed until it can be fully functional. I have to say it's a neat
solution to scale and have almost instant transactions in a peer 2
peer, distributed and trustless way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/14/2015 6:19 PM, Paul Sztorc wrote:
> LN transactions are a substitute good for on-chain transactions.
>
> Therefore, demand for on-chain transactions will decrease as a
> result of LN, meaning that fees will be lower than they would
> otherwi
So what exactly is used to create the normalized txid (sha256 hash of
what data)? I've read in the linked BIP draft that it will strip the
'malleable parts' but didn't understand what exactly will be used to
calculate the normalized transactions ids and how will the change apply
retro-active for th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Right. Wallets are covering malleability in acceptable ways. Normal
user to user payments aren't (or at least shouldn't be) affected by
malleability.
Problems appear in second level and third level malleability, when
Alice sends txB to Bob which spe
What will be the actual effect over wallets?
Say I have the private key for a dormant UTXO older than the
consensus-critical maximum UTXO age. The UTXO is not part of the cache.
So I setup a full node and import my old private key (wallet.dat). Will
I even see the correct balance (where will it ge
On 6/23/2016 1:56 PM, Peter Todd via bitcoin-dev wrote:
>>
>> I don’t know if you are opposed to organizations that have AML requirements
>> from using the bitcoin blockchain, but if you aren’t, why wouldn’t you
>> prefer an open source, open standards based solution to exclusionary,
>> proprietar
Hi,
I can clearly see some advantages for such a feature, but it's kind of
in conflict with Bitcoin's fundamental design. This design might be
problematic when it comes to hacks/thefts, but it's what gives Bitcoin
strength and make it differentiate from other currencies:
* reversal of transaction
t. khan via bitcoin-dev wrote:
> BIP Proposal - Managing Bitcoin’s block size the same way we do
> difficulty (aka Block75)
>
> The every two-week adjustment of difficulty has proven to be a
> reasonably effective and predictable way of managing how quickly blocks
> are mined. Bitcoin needs a reas
t. khan wrote:
> Miners 'gaming' the Block75 system -
> There is no financial incentive for miners to attempt to game the
> Block75 system. Even if it were attempted and assuming the goal was to
> create bigger blocks, the maximum possible increase would be 25% over
> the previous block size. And
Andrew Johnson wrote:
> "You miss something obvious that makes this attack actually free of cost.
> Nothing will "cost them more in transaction fees". A miner can create
> thousands of transactions paying to himself, and not broadcast them to
> the network, but hold them and include them in the blo
29 matches
Mail list logo
