Bitcoin Forum
May 30, 2024, 02:00:32 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 [143] 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 ... 288 »
2841  Bitcoin / Development & Technical Discussion / Re: Transaction Malleability Reloaded on: March 19, 2014, 01:26:29 AM
You got a negative trust rating because you've hyped bogus and deceptive security claims multiple times and tried to charge people for exploit tools that didn't. But hey, you could still collect on that 50 BTC bounty I offered you for your last set of claims, and I'll even remove the negative trust to boot.
2842  Bitcoin / Development & Technical Discussion / Re: Transaction Malleability Reloaded on: March 18, 2014, 07:29:19 PM
going to need a little more than that from someone who's already raised questionable alarms before
You mean outright fraudulent alarms. You note even here he says "probably".

I call bullshit.  Real cryptanalysis is specific.
2843  Bitcoin / Electrum / Re: Electrum 1.9.8 released on: March 18, 2014, 03:04:34 PM
FWIW, for those curious— the thread on the encryption issues: http://sourceforge.net/p/bitcoin/mailman/message/32107008/   (I made several posts after the first one too)
2844  Bitcoin / Development & Technical Discussion / Re: TX Only Valid Until X Block on: March 18, 2014, 07:48:20 AM
An expiry there is practical but still not guarantee, since anyone recorded the transaction can rebroadcast it again.
Outright enforced expiration is not reorganization safe and can cause coins and their history to be suddenly invalidated even in the complete absence of an attacker. This exposure different for coins based on their depth would degrade the fungability of the coins, and avoiding it is one of the reason that generated coins cannot be spent for 100 blocks.

There is, however, some work going on towards allowing single transaction refunds that would allow you to easily spend a coin to an alternative output in order to cancel it after some time has passed.  This addresses some but not all of the use-cases for expiration (as well as many other use cases) without the risks. I should have a proposal on the mailing list in a few days— I'm still hammering out the details of exactly what I'll be proposing with a few other people first.
2845  Bitcoin / Group buys / Re: HF Chip Group Buy on: March 17, 2014, 08:56:40 AM
If Hashfast fails to deliver, as they're currently doing for may customers— including yourself, I believe— how will you make your buyers whole? You should also be aware that there are people currently suing hashfast and this may result in making it harder for them to deliver. You should also be aware that HF has a history of unilaterally changing terms and claiming that not adopting their new terms voids all their obligations.

Does your "Caveat Emptor" mean that if Hashfast does not deliver you will do nothing?

Beyond my basic moral reservations with giving more funds to a company who is currently ripping so many people off— I suggest that instead of just collecting funds from people and give them to the black hole of fraudulent behavior that is hasfast you collect funds into escrow (e.g. with bitrated.com) and only pay hashfast on delivery.
2846  Bitcoin / Development & Technical Discussion / Re: Bitcoin Qt: lockunspent broken? on: March 17, 2014, 08:05:46 AM
Works fine here:


[gmaxwell@helmholtz tmp]$ bitcoin-cli listlockunspent
[
]
[gmaxwell@helmholtz tmp]$ bitcoin-cli lockunspent false '[{"txid":"76a914a86e8ee2a05a44613904e18132e49b2448adc4e688ac","vout":0}]'
true
[gmaxwell@helmholtz tmp]$ bitcoin-cli listlockunspent
[
    {
        "txid" : "0000000000000076a914a86e8ee2a05a44613904e18132e49b2448adc4e688ac",
        "vout" : 0
    }
]
[gmaxwell@helmholtz tmp]$ bitcoin-cli lockunspent true '[{"txid":"76a914a86e8ee2a05a44613904e18132e49b2448adc4e688ac","vout":0}]'
true
[gmaxwell@helmholtz tmp]$ bitcoin-cli listlockunspent
[
]
[gmaxwell@helmholtz tmp]$
2847  Bitcoin / Development & Technical Discussion / Re: I don't think 'Pi' is a valid public key... on: March 17, 2014, 04:36:07 AM
It's arguably that bc.i should display something more useful there... but at the end of the day the key point remains that the bitcoin system itself doesn't have addresses— addresses are a wallet layer construct and any attempt at mapping back from the chain to addresses is going to have some limitations.
What do you mean, Bitcoin itself doesn't have addresses? A recipient in a tx is nothing more than an address, right? Regardless of how we represent it, but I mean it's not an actual public key or something.

Or maybe I have a wrong idea of what an address is, but to my knowledge an address is nothing but a RIPEMD160 hash of a SHA256 hash of a public key that corresponds to some private key...?
An address is just a human friendly way to encode a template for a scriptPubKey. Transactions do not contain an address for each of their outputs, however, just the resulting scriptPubKey. There is no guarantee that you can reverse the operation for all transactions.
2848  Bitcoin / Development & Technical Discussion / Re: Rapid decrease in mining power? on: March 17, 2014, 04:33:44 AM
>50% permanent reduction in mining
Whoptie do, blocks are expectation 20 minutes for a month.

Difficulty being hesitant to change improves security against isolation and decreases the amount pumping of difficulty by variance.
2849  Bitcoin / Development & Technical Discussion / Re: I don't think 'Pi' is a valid public key... on: March 16, 2014, 08:54:33 PM
EC is hard enough - I can't even begin to imagine the consequences of returning a point that's not on the curve. Does it just mean there is no private key? Or is there an infinite number of private keys?
The missing points are on an alternative curve (the quadratic twist) and have a discrete log (a private key). For some curves used for cryptography the twist is not cryptographically strong— meaning the discrete log is 'easily solved' there— though ours is acceptably strong. It's still important that any verifier check the that the pubkey is on the curve (and especially important for anything doing ECDH).

It's arguably that bc.i should display something more useful there... but at the end of the day the key point remains that the bitcoin system itself doesn't have addresses— addresses are a wallet layer construct and any attempt at mapping back from the chain to addresses is going to have some limitations.
2850  Bitcoin / Development & Technical Discussion / Re: Dual SNARK: How to make ZKP with trusted initilization trustless in some cases. on: March 16, 2014, 08:25:45 PM
Why do you say "because it's zero-knowledge miners couldn't come along and replace the outputs like in a plain hash-locked transaction" ? If I understand this paragraph (and your last comment in this post) correctly, the payer has to specify a specific payee that can redeem the coins (rather than allowing anyone who knows a solution to the Sudoku puzzle to redeem the coins) ? If so, this can be done outside the snark, as we normally do in Bitcoin by requiring the ScriptSig input-script to provide a signature for a specified address/pubkey of the payee, in order to prevent miners from replacing the output. Is there any beneficial reason to enforce the payee's identity inside the snark, as you seem to imply here?
Perhaps not. I probably picked a poor example— and perhaps there isnt one— to describe a motivation for doing this.  Really when the payee is designated I think you can almost always completely remove the proving process from the cryptocurrency.

Quote
Also, if I understand correctly then the protocol here isn't non-interactive, i.e. the payee sends to the payer via a private channel an encrypted solution s0 encrypted under symmetric key k0, and then the payer broadcasts the snark transaction that should reveal (in the clear) k0, so that only the payer will know the solution?
It's inherently interactive but it could potentially be asynchronous. 

Let me expand the idea further so that the application is more clear.   Say we make our SNARK circuit a universal circuit (like vntinyram) which takes a hash of the program as a public input (and the program itself as a private input).   Lets also assume that you and I are members of a trading club which frequently trades puzzle solutions for coins amongst its members.

Every member of the trading club compiles and the tinyram circuit and produces a ECDSA private key. They publish the verifier key and public keys to all the members of the club and (via some sibyl resistant process) the club produces a hash-tree over these verifier keys and the public keys which everyone in the club agrees is correct.

Now I can form a transaction which offers a coin to someone who can produce either dual SNARK proofs (or SNARK+sig), such one snark is mine, and the other is any which is not mine in the list (by providing the verification key and proving membership in the set committed in the transaction).

(If you don't-dual snark, and replace the hashtree with a ring signature of all the club members except me (or turn the hashtree approach into a ring signature by running selection and blinding in zero knowledge), then the identity of the redeeming party can be private and unknown even to me.)

In any case in this example there was interaction, but it was all in a setup phase, and the redemption can be asynchronous and one-shot.

Quote
If my understanding above wasn't way off, then isn't it enough here to require the payee to provide his digital signature (in additional to the proof that passes the snark verification), and because the payer cannot produce a signature for the corresponding pubkey of the payee, he cannot double-spend by providing a false proof (that he can produce because he knows the snark initialization), at least until some nlocktime expired where he'd spend the output via a transaction that the payee already signed for him.
Maybe, though this has weakness when you want an 'nlocktime' rule which is more complex than nlocktime.  E.g. transaction pays you if you present a receipt from your bank that the payment went through, it refunds to me if I can present proof from my bank that the transaction was reversed... then only after some very long timeout does the nlocktime come into play.

It seems to me that for non-interactive proofs (as in CoinWitness), the need to avoid a trusted initialization cannot be overcome. And on the other hand, trusted initialization isn't really an issue in interactive ZK proof scenarios? But please elaborate on any observations that I could be missing here...
I agree. Though I'm not sure if non-interactive is the quite the right criteria it fails, I think it fails publicly verifiable (yes, the CRS schemes are 'publicly verifiable', but only with trust that is not really acceptable). The interactive schemes are often easy in part because there is a designated verifier.

I don't seek to say that trusted init can replace non-trusted, it really cannot for many things. I'm just exploring the space that tools with trusted initialization can be applied.
2851  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: up to 800GH/s on: March 16, 2014, 12:13:49 PM
Oh brother, could you possibly be more maudlin and self-pitying?   Roll Eyes
A 105% refund is not "nothing" no matter how much you prefer a 600% windfall.
No court is going to ignore the fact you refused a refund in legal tender.
Have you read a Federal Reserve Note lately?  It does what it says on the label (settle all debts, public and private).
You did not offer me a refund, you offered me a settlement— as was plainly stated. The settlement was for a fraction of what you owe me according to our established agreement and had burdensome additional terms which I have never and will never agree to. (If we're to be pedantic: You also did not offer me federal reserve notes, fwiw.)

No court is going to ignore that you ignored a mountain of letters from me and my months long good faith effort to sort this out in a mutually agreeable manner, no court is going to ignore that you've never offered me a _refund_ just an additional contract "settlement" for a fraction of our agreed on terms. No court is going to ignore that you you're now publicly claiming that you're not going to pay me anything at all.

As I pointed out in prior (I believe now deleted) messages: I would happily take alternative compensation for your default and would even prefer alternative compensation if it was mutually beneficial. What I wouldn't accept is a tiny fraction of a refund plus a "disparagement agreement" while you walk away with a huge windfall and leave dozens of other customers screwed over here— while the "disparagement agreement" left me less able to help them.

But speaking of court— you're saying you're so confident about the outcome, OKAY— where is my release from the forced arbitration so we can actually take it to court without a months long dispute over the proper venue?
2852  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: up to 800GH/s [Non Self Moderated] on: March 16, 2014, 11:43:03 AM
FWIW, it looks to me like they're selectively locking the other thread when they're not at the computer and can't be vigilantly deleting messages. Kinda crazy.
2853  Bitcoin / Development & Technical Discussion / Re: I don't think 'Pi' is a valid public key... on: March 16, 2014, 11:34:45 AM
It's an output, and it's unspent. Bitcoin blockchain rules do absolutely nothing with the content of scriptpubkey until its spent.
2854  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: up to 800GH/s on: March 16, 2014, 11:20:18 AM
You have time to complain to the forum, bother the State of Californa, and hire a lawyer.
I have a standing relationship with an attorney for a multitude of reasons.  I don't know why you keep talking about "bother the state of california", I believe I've not yet ever communicated with the state of California on any matter what-so-ever, and certainly not you or your company. You need to discontinue your lying here.

Quote
More like, you know your quest for a ~600% gain for doing nothing is doomed to fail if it ever reached a proper venue.
Okay, release me from the forced arbitration clause so that there isn't ton of time wasted arguing about the venue— since you're so confident that you'll prevail— and I'll go head with lawsuit now that you've _finally_ admitted that you're planning on actually returning nothing at all— and not leaving me thinking that you just have not been getting my letters.

By taking my funds and giving absolutely nothing, no refund no product you are a thief. And perhaps really what I should be doing is perusing criminal charges. Your theft is not just a civil matter at this point: No theory of law enables you to take peoples funds and give them nothing and then argue that they've somehow forfeit your obligation because you've successfully ignored all their attempts to communicate or negotiate and they wouldn't take a tiny fractional one-sided 'settlement' with onerous additional terms.
2855  Bitcoin / Development & Technical Discussion / Re: Berkeley Database version 4.8 requirement unsustainable on: March 16, 2014, 08:10:08 AM
why not define an specific database for bitcoin to decrease the blockchain?
I believe BerkeleyDB save a lot of metadata for it's own work/features that maybe we dont need them at all.
BDB is _only_ used for the wallet. The blockchain itself is stored as raw blocks.
2856  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: 400GH/s on: March 16, 2014, 06:26:49 AM
i think you got a chance there.
Sadly, I don't because I simple don't have the time— or emotional tolerance— to see these guys through to court. Fortunately other people are already in the process of suing them, so some amount of justice may still be served.

I started the heavy prodding in public when I saw they were soliciting more rubes to screw over, with only a mild hope that I'd ever see a dollar or a Bitcoin out of them— that maybe if they saw they they were going to be able to get away with the highly profitable task of pulling in more victims without complaint they might try to rescue things with their past customers.  I think that at least the recent noise has been successful at increasing a lot of awareness, and maybe saved some people a $6k loss, so thats all good.

If there is anything someone thinks I can easily do to help them recover please let me know.
2857  Economy / Service Discussion / Re: CampBX [btc] missing on: March 16, 2014, 01:26:38 AM
FWIW, Campbx seems to have lost my deposit of testnet BTC.  Glad they have a testnet site so that I could see that their service is having problems without using real coins! Smiley
2858  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: 400GH/s on: March 15, 2014, 09:35:40 PM
So there is a gap in lawmaking and HF is using this gap to commit fraud.
I don't really agree there. This is what contracts exist for. The law doesn't have to forsee in advance every possible business contingency.  There is no basis in law that says that you can just ignore a contract when it suits you.
2859  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: 400GH/s on: March 15, 2014, 09:31:37 PM
Just out of curiosity, you stated in the other thread that your deadline was the 31 of January. Batch 1 deadline was the 31 of December, so you are batch 2, right?
Gah no. I started to type January 1st and then realized the actual date was Dec 31st and didn't fix the month. My purchases were August 14th and September 1st, both Batch 1. (thanks for pointing that out, I fixed it)

They sent the revised terms to me on 08/21. I just personally consider them binding both due to the second purchase and because I talked to them after, considered immediately demanding a refund but didn't— because frankly the revised terms seemed more realistic to me... I was worried that they'd be a day late and get slammed with refunds and that didn't strike me as fair or wise. So if anything the contract revision increased my confidence... how foolish I was.
2860  Bitcoin / Hardware / Re: HashFast announces specs for new ASIC: 400GH/s on: March 15, 2014, 09:25:33 PM
The bottom line is that money is power.
Well, hey, some of us still have money here, and their 90%-100% losses on HF so far haven't left them broke.  Is there some slot where I can insert money and receive justice? I too am unhappy with them getting away with the fraud— even more so than my financial loss. I'm willing to double down on my losses if I was reasonably confident that the result would be them not getting away with it, because I'm very concerned with the long term effects on the mining ecosystem if its possible for hardware vendors to freely get away with fraud. What I don't have an abundance of is time.

I was thinking of perhaps funding some bounties for things like most effective community action to prevent others from getting defrauded by hashfast, but I'm not sure I have time to administer it— and esp. in terms of figuring how how to convince people that I'm being serious when I say that I really don't want anything illegal done.
Pages: « 1 ... 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 [143] 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 ... 288 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!