Bitcoin Forum
May 25, 2024, 08:39:31 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 »
81  Bitcoin / Project Development / Re: BitcoinAverage.com - bitcoin price index on: July 26, 2014, 12:58:51 PM
Bitstamp has been marked as "unreachable since 25 Jul, 11:22 UTC" and ignored, but the Bitstamp API appears to be working just fine.
82  Bitcoin / Development & Technical Discussion / Re: Multisig Idea -- Mandatory vs. Optional Signatures. on: July 21, 2014, 07:08:52 PM
Right now, the above is impossible, because 2 of the co-workers could just sign the transaction without any approval from the boss.  What about slightly changing the redeem script so you can define the user & boss keys mandatory, and the 3 co-worker keys optional.  Would that be possible?

Scripts are more flexible than just m-of-n. In particular you can use AND and OR to chain m-of-n conditions among other things. User AND Boss AND 1-of-3 coworkers.
83  Bitcoin / Project Development / Re: Ripple: A Distributed Exchange for Bitcoin on: June 16, 2014, 10:38:00 PM
It's sold as a way to transfer USD or JPY or BTC or any store of value. It's not.

It is a way to trade IOU's, that rely on your trust in the entity that issued them.

The same is true for wire transfers.
84  Alternate cryptocurrencies / Altcoin Discussion / Re: How the Ripple payment network and XRP are different from Bitcoin on: June 16, 2014, 06:45:57 AM
the problem with ripple is you have to make it onto the UNL list, to be part of the consensus.

There's no such thing as the UNL, every node chooses its own UNL.

Quote
You can't just join.

More precisely, you can't force others to put you on their UNL, since they like you are free to choose their own.
85  Bitcoin / Project Development / Re: Ripple: A Distributed Exchange for Bitcoin on: June 05, 2014, 12:02:06 PM
This thread remains a reliable source of people to block.
86  Alternate cryptocurrencies / Altcoin Discussion / Re: Turing complete language vs non-Turing complete (Ethereum vs Bitcoin) on: May 08, 2014, 11:20:07 AM
Merkelised Abstract Syntax Tree. Its root hash gives a summary of the whole AST, just as with a Merkle root in a block. This allows you to give the part of the script that is actually executed when spending, without having to list the whole possibly very lengthy script while still proving you've only used branches from the original AST.
87  Bitcoin / Project Development / Re: Coinsigner decentralized exchange crowd funding campaign and shedding some light on: April 28, 2014, 10:42:32 AM
Hi, mmeijeri, have you done anything on this area? any relevant info?

Lots of multisig activity right now. Several groups are working on multisig auctions / ebay clones. Bitrated.com facilitates third party escrow. Virtual-notary.org layers its services on top of the blockchain. Several people have suggested layering distributed storage protocols on top of the blockchain in a way that allows you to store large amounts of data for a fee without bloating the blockchain, while still securing the stored data.
88  Bitcoin / Development & Technical Discussion / Re: Private keys in RAM on: April 23, 2014, 10:15:48 AM
Interesting OpenSSL patch by Akamai related to this, via @csoandy on Twitter:

http://marc.info/?l=openssl-users&m=139723710923076&w=2

Turns out this patch doesn't work at all, several experts panned it.
89  Economy / Securities / Re: NEO and BEE talk (unmoderated) on: April 19, 2014, 12:46:04 PM
pwnt

Heh, I like your grammar. :-)
90  Economy / Securities / Re: NEO and BEE talk (unmoderated) on: April 19, 2014, 12:00:41 PM
Bitcoiners actively allow scammers and dreamers, by checking nothing, trusting anything 'because it's Bitcoin' and then accusing any criticism as FUD.

That is changing quickly though and has absolutely nothing to do with Bitcoin itself or even any supposed libertarian philosophy. MtGox was a centralised point of failure in a decentralised system. Centralised exchanges should have no role in a decentralised system.
91  Economy / Securities / Re: NEO and BEE talk (unmoderated) on: April 18, 2014, 11:35:51 AM
The former COO and former Compliance and Risk Management Officer have posted a statement on Reddit.

http://www.reddit.com/r/Bitcoin/comments/23cjd9/the_full_picture_of_former_neo_bee_employees/
https://twitter.com/Papaphoenix/status/457118162925133824
92  Economy / Securities / Re: Neo & Bee talk (spam free thread) on: April 15, 2014, 05:15:55 PM
I'm guessing it's a change of address, but we'll see.
93  Economy / Securities / Re: Neo & Bee talk (spam free thread) on: April 13, 2014, 10:25:28 AM
Easy to say that in hindsight.
94  Economy / Securities / Re: Neo & Bee talk (spam free thread) on: April 12, 2014, 05:45:19 PM
I do not know more about this case than any random reader of this thread.  However, the transition from incompetence to criminality seems to be common in similar situations.

I agree this is a plausible possibility in this case.
95  Bitcoin / Development & Technical Discussion / Re: Private keys in RAM on: April 12, 2014, 12:36:55 PM
Interesting OpenSSL patch by Akamai related to this, via @csoandy on Twitter:

http://marc.info/?l=openssl-users&m=139723710923076&w=2
96  Economy / Securities / Re: Neo & Bee talk (spam free thread) on: April 09, 2014, 02:39:41 PM
So how do "weak minds" cause coins and fiat money to disappear? They don't.
97  Economy / Securities / Re: Neo & Bee talk (spam free thread) on: April 09, 2014, 02:10:36 PM
The coins and fiat money didn't disappear because of a "hatred campaign".
98  Bitcoin / Development & Technical Discussion / Re: Private keys in RAM on: April 09, 2014, 12:43:17 PM
Well, that too of course, but 2/3 of the web was vulnerable to this one, whether they updated regularly or not. Layered defence is good.
99  Bitcoin / Development & Technical Discussion / Private keys in RAM on: April 09, 2014, 09:43:01 AM
After the heartbleed scare I've been thinking if perhaps we shouldn't make an effort to store private keys more securely. This isn't a new issue of course, and there are lots of existing techniques and best practices I'm only dimly aware of, including things like PKCS #11 and HSMs. I know work is also being done on Bitcoin-specific hardware solutions like Trezor.

Maybe we all need to move to hardware-based solutions in the future, but maybe there is also room for software-only solutions. Right now most people don't use specialised crypto hardware, and I was wondering if it would help if signing operations were at least located in a separate process with an independent address space. There is a library called SoftHSM which is a software-only implementation of PKCS #11. I think it's supposed to be linked directly to the application, but maybe it can be used as a starting point.

So, what do you think? Would this be a useful near-term improvement, or an undesirable half solution that discourages people from using dedicated hardware, if we believe that's the real solution?
100  Alternate cryptocurrencies / Altcoin Discussion / Re: Ripple vs Bitcoin on: April 08, 2014, 10:29:22 PM
I still dont get how consensus will work with ripple. Is it POS?

No, every validator specifies a list of other validators he wants to reach consensus with. See https://www.youtube.com/watch?v=pj1QVb1vlC0 and https://ripple.com/wiki/Consensus.
Pages: « 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!