Was any of the funding for APICoin used in the development of this project?
|
|
|
Haven't heard anyone talk about it but on here.. so I don't consider that strong. A simple gui was needed from grandma that couldn't be done in 3 years of trying? Is that strong software development to you?
That you don't understand the problem domain is more a reflection on you than on OT.
|
|
|
Its sad but true that I think OT never really took off because it couldn't be used as a get rich scheme or P&D The OT client for grandma offered what a 500btc bounty or something crazy? But noone ever did it and I don't think those bounty awarders are still around to offer that kinda money for the nice client... otherwise I'd prob take a stab at it. i think its going strong, its the best solution not a failed one. The reason you're not hearing much about OT is that Monetas is spending a lot of time working on voting pools, which are a hard problem to solve and also a backend technology. When exchanges start using voting pools to handle customer deposits, there will be a great many OT users who won't even realize they're using it.
|
|
|
Well, compared to stocks and forex itīs just pocket lint.
So, why doesnīt BTC have any volume to speak of ?
What keeps big investors off ?
Is it the totally unregulated and scam-ridden marketplace ?
Is it the primitive "exchanges" , which may or may not exist tomorrow ? Bitcoin is developing in a way that makes it naturally more resistant to those parasites. I hope they stay away for as long as long as possible. Let them stay in their own little sandbox and eventually 100% of the paper that nobody else wants.
|
|
|
For instance, triple-signed receipts used by Open Transactions (see opentransactions.org/...) may be distributed to the entire network. OT is not capable of forming the kind of distributed consensus needed to create a currency like Bitcoin. Triple signed receipts are fine for recording contracts, though.
|
|
|
but sidechains are not competitors The same value can not be held simultaneously in the main chain and in a side chain.
|
|
|
He may be referring to ancient history. More recently, the price peaked at 259 USD on April 10, 2013, and bottomed at 275 USD on October 5, 2014. Not quite, but pretty close...
Close, but not quite.
|
|
|
I will be taking profits at $1,999 and waiting for the retreat to $1,203 before getting back in again. How many time has the Bitcoin exchange rate retreated back down to the value of a previous peak after achieving a new one? 3 Which three times are you talking about?
|
|
|
Generally speaking, there are two different ways in which a miner can behave: they can operate in good faith or they can grief.
Griefer miners have to pay a real cost for their bad behaviour - they expend significant quantities of electricity and capex depreciation which they will never recover.
What if a Bitcoin miner decides to grief the Namecoin blockchain? Mine empty blocks, intentionally orphan valid parts of the chain, run difficulty up and then pull out, attempt double spends of Namecoins, etc.
Their electricity and capex is paid for by the Bitcoins they mine. Sure, they have to spend a little bit in bandwidth to run a Namecoin node, but that cost is insignificant compared to the cost of mining Bitcoin.
This is why merged mining doesn't provide the kind of security that people think it provides. The only security comes from the goodwill of the mining pool operators, without strong economic incentives that make good behaviour much more profitable than bad behaviour.
Just like proof of stake, and also just like central banks.
|
|
|
I will be taking profits at $1,999 and waiting for the retreat to $1,203 before getting back in again. How many time has the Bitcoin exchange rate retreated back down to the value of a previous peak after achieving a new one?
|
|
|
When a Bitcoin miner starts merge mining Namecoin, how much more opportunity cost do they forfeit compared to the case where they only mine Bitcoin?
The time, electricity, and capex needed for mining Bitcoin doesn't count because that cost is paid for with Bitcoin. From the perspective of Namecoin's security model, it's not an opportunity cost.
If a Bitcoin miner wants to attack Bitcoin's ledger, they have to pay a real cost for it. If a Bitcoin miner wants to attack Namecoin, the cost of the attack is effectively free.
We know how easy it is for Bitcoin miners to attack other double SHA256 ledgers, because they've done it before.
At best, merge mining creates security equivalent to proof of stake.
|
|
|
Are you insinuating that this mechanism leads to more centralization and therefore more counterparty risk?
Stop playing around and just say what's on your mind, you don't appear to me to be someone who usually play the cat and mouse game. I'm insinuating that you have no idea what you're talking about with regards to counterparty risk, centralization, or distributed consensus. The reason I know this is because of how you worded your previous comment - your scenario was a "100% merge mined" sidechain. Of course that makes sense, right? 1. Hashing is what makes Bitcoin secure 2. More hashing equals more security 3. Therefore any chain that has an equal amount of hashing power as Bitcoin will be equally secure. Sounds great, except the first premise is false, therefore so is the conclusion. Hashing isn't what secures Bitcoin - opportunity cost is what secures Bitcoin. Anybody who doesn't understand that is not qualified to evaluate the security properties of sidechains.
|
|
|
Please point out the additional counterparty risk of a 1:1 open-source & properly implemented sidechain that is MM 100%. Please explain the mechanism via which merged mining solves the distributed consensus problem.
|
|
|
no counter-party risk.
Bullshit. Find one credible source who will go on record saying that sidechain units carry zero counterparty risk compared to bitcoins. Actually the sidechains whitepaper was fairly explicit about saying the opposite. Reducing counterparty risk is a worthy goal, however one can't build solutions to a problem that one refuses to acknowledge. Anybody who thinks that counterparty risk for promissory notes can be eliminated is delusional. Managed? Sure. Reduced? Absolutely. Eliminated? Never.
|
|
|
I see something happening here that's been a long standing problem in the Bitcoin space, especially in "Bitcoin 2.0" circles.
Quite a few people, sometimes out of ignorance and sometimes out of malice, blur the lines between money and promissory notes.
|
|
|
i would much rather use OT federated servers from what i know about it. At the very least, it won't take two days to move funds into and out of them.
|
|
|
A lot of investors think that the main purpose is payments, so they invest in diverse bitcoin related services companies. I think payments in itself does not drive the price, only the urge to hold bitcoins. Fortunately, that is a future side effect of creating many new payment customers, so I am happy with that.
... and we're back to the quantity of money formula ! The "side effect of holding bitcoins with the purpose of doing payments" is *exactly* what that formula expresses ! Of course the payments in itself do not drive price. The payments (Q) plus the "holding" (1/V) that goes with it, does. But this was also my worry: if bitcoin payments are going to be: 1) acquire bitcoins on an exchange 2) do your payment immediately with it (after a few blocks) 3) the seller receives the payment 4) after a few blocks, converts them back into fiat Then this corresponds to a very high velocity (a very low time to hold) and you can buy *a lot* of stuff with a few bitcoins at a relatively low price that way. It's hard to tell from this post whether or not your explanation is correct. In your scenario, "you can buy *a lot* of stuff with a few bitcoins at a relatively low price" is true if by "price" you mean the price of a bitcoin in terms of stuff. A higher velocity means a higher P in the quantity theory of money formula, where P is the price of stuff in terms of money.
|
|
|
Ideally, I like to see us move forward with the hard fork within the next 12 months, sidechains explored using federated servers, and the risks and rewards of adding support for SPV proofs to the protocol analyzed in much greater detail from the technical perspective, but also from the economic, legal, and game-theory perspectives too.
Ideally, I'd like to see a development roadmap for the protocol, with clearly-defined criteria for determining what goes in and what does not. Unfortunately a prerequisite for that is a common agreement on goals.
|
|
|
|