Bitcoin Forum
April 19, 2024, 12:33:57 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 [6] 7 »
101  Bitcoin / Project Development / Re: Building the Next Generation of Crypto-Currency (developers required) on: June 03, 2013, 01:58:17 PM
Am I correct, that mechanisms like colored coins, would not work with this kind of chain?
102  Bitcoin / Project Development / Re: Building the Next Generation of Crypto-Currency (developers required) on: June 03, 2013, 01:12:55 PM
Quote
But I wonder whether having the proof chain in the picture might make it possible to reduce the amount of work that needs to be proved for every block in order to keep the network secure. My idea (intention) would be to keep the work/difficulty down to a level that would allow CPU mining instead of GPU.
It's impossible to keep the difficulty down at a CPU-friendly level because the difficulty must shift according to the total amount of hashing power miners are throwing at the network. Without changing the difficulty in that way we cannot control the rate at which new coins are created. Obviously though we do plan to include some sort of scrypt-based mining system to make it more ASIC resistant.
Yes, I do understand the need for having a difficulty and the ability to change the difficulty. If the presence of the proof chain doesn't present a possible path to generally lower difficulties, then perhaps a change to the sCrypt that would use registers or features present in a CPU but not (currently) present in a GPU or ASIC -- or something. I don't know what the answer is, but would suggest and request that we all keep our eyes open for methods that would 1) allow for less wasted energy/resources in the mining process, and 2) keep mining more distributed. Just imagine, the MBC coin client is light enough for any and every user to easily be a full node, and the mining process is gear to make it profitable for any user to commit a processor or two to mining. I would love to see millions of small users generating a few kH/s each, instead of a few hundred (or a few dozen) huge players generating 10s of MH/s or GH/s. (As John Lennon said, "You may say I'm a dreamer..., but I'm not the only one...".)

Why do you think that GPU/CPU would be more energy efficient compared to ASIC's?
ASIC's are much more energy efficient. You just pay more for the custom designing/manufacturing of ASIC's, but in the end with ASIC's you have much less power consumption.

*EDIT*: So in principle you can say less power consumption would automatically mean more centralization. The only way to have both (decentralisation and power efficiency) at the same time is if you use a hybrid of proof-of-work and proof-of-stake
103  Bitcoin / Project Development / Re: Building the Next Generation of Crypto-Currency (developers required) on: June 02, 2013, 02:32:37 PM
Wouldn't it be better to improve Bitcoin rather than creating a new currency?

The problem with the increasing blockchain size is within the bitcoin protocol itself. As mentioned in the white paper there is the thread about 'ultimate blockchain compression' for bitcoin. But it is by far not as good as this new proposed coin. It only tries to fix some effects without really fixing the underlying problem. If you have a proposal, which could improve the existing bitcoin protocol which is comparable to the performance of this proposal here, then everyone would definately like to hear it.

This new coin proposed by bitfreak is really designed from a new perspective to reduce the bloat which we see in BTC. So I think it really deserves to be implemented and tested!

Btw, it adds some other important features, as aaaxn said:
I think the most important one is that secure 0-confirmations would be possible. I would definately add this to the first post.
104  Bitcoin / Project Development / Re: SSL logs as proof of money transfer for p2p exchanges on: June 01, 2013, 07:18:47 PM
I have a new suggestion, melding together several of the ideas already mentioned:
...snip...

A problem with the approach to always have the proxy on the machine of the BTC-seller is that they might not be online at the same time. How could they agree to a specific online time? Should they specify this in their trade? In principle the BTC-buyer could just say that he couldn't do the transfer because the BTC-seller was always offline when he wanted to do it.

Although it's clearly not ideal to have this synchronization, this seems to be a less important issue. Counterparties displayed would be restricted to those who are active on the network at the time you are looking to trade. Both sides have to agree to a price as well as certain other settings possibly, and then the proxy-ed session to the bank can take place. Importantly, the BTC seller (acting as proxy) doesn't actually have to DO anything during the proxy session (doesn't have to sit at their computer), just has to be online. I think realistically they would want to stay around though and get a confirmation message that the encrypted data from the session was stored correctly.

If the BTC seller fails to store that encrypted data, they have forfeited the right to their (escrowed) BTC in case of a dispute. That works both ways; if the BTC buyer (the one who used internet banking to make a transfer) loses the SSL session key which decrypts the data, they also would forfeit their right to the BTC in case of a dispute.

I am just comparing the two possibilities which you presented:
#1 The BTC seller is the gateway
#2 A fourth party is the gateway

I see only negative points with #1 and only positive points with #2. Let me elaborate:

I think many users would like to trade without recording their online-banking session if there is no dispute. You already proposed earlier that the method could be used after a dispute only. I personally would like that much more. But then you would have to wait maybe 1-3 days until the wire-transfer cleared and only then you would have to eventually enter the dispute process and use the proxy. It's not quite clear that the BTC seller is online at that time.

I, personally, would try to minimize the use of the proxy, because proxying an online-banking connection increases the risks (i.e. man-in-the-middle attacks as described in CVE-2009-3555). Your risks increase even more if you cannot use SSL-renegotiation during this banking session (i.e. your full recorded SSL-session is exposed to one party and could be decrypted using your master key, which you have to expose at least to another party). I personally would like to minimize both these risks and I also don't like to change my online-banking password so often.

Maybe you could persuade me to always expose my online-banking-session and the corresponding session-master-key if you could elaborate more on your proposal to use
Quote
(a)random choice, possibly more than once and (b) prevention of Sybil attack by cost of identity creation.
if you find 100% secure way to do this, then maybe I will trust this. Otherwise, I would prefer to trade without recording my SSL-session.

So in summary:
if we use option #1 the BTC seller is the gateway
--> BTC-seller and BTC-buyer have to be online at the same time
--> Only instant trades are possible (not possible to first wait for the clearing of the money-wire before a dispute)
--> Every trade has to use recording of SSL-sessions.
--> Much higher risks

in contrast, with option #2 where a fourth party is the gateway
--> asynchronous trades are possible
--> recording of SSL-session only in case of disputes
--> reduced risks

So why not allow p2p-trades with a lot of different contracts, depending on what risks someone is willing to take? I think the worst option is to only implement the solution with the highest risks, isn't it?


Weaknesses:
1. the bank may frown upon the payer logging into his bank from random IPs. But we discussed this earlier and it seems not to be a serious weakness.  
2. The payer can flood the p2p pool from which the gateway users get selected by his accomplices. If the payer and gateway user are in cahoots, they can spoof the whole SSL session.
3. To mitigate #2, the gateway user should be the beneficiary of the payment. (The beneficiary has no interest to defraud himself), which leads to ...
4. If the beneficiary is the gateway user and over time has a lot of those who pay him, the bank will flag the beneficiary's IP because there will be many users of that bank logging into their accounts from the same IP.

The problem which you describe in #2 applies also to the selection of the escrow agent. How would you make sure that the escrow agent is really a third party and not in cahoots with either the seller or buyer? Probably by some mechanism to randomly choose the escrow. So if it works there, why not use the same mechanism for the gateway? So I would say your point #3 doesn't make sense, especially if you think about the problem that they both have to be online at the same time it is better to select a random user from the pool?
I agree that the 4th party is an extra level of architectural complexity that is worth avoiding if it doesn't really bring a benefit.

I don't see the extra level of complexity, because you have to implement some form of randomly choosing the escrow anyway. So you can also use the exact same algorithm to select an independent gateway.

Quote
To make sure that all 4 parties (seller,buyer,escrow,gateway) are really different persons, it would even make more sense to link p2p-accounts to real-world-bank-accounts. This would reduce the risk that someone could flood the p2p pool, because nobody has arbitrary many bank accounts.

The only risk left once we move to the model I describe in post 61 is the collusion between the escrow and either the buyer or the seller. This is mitigated by (a)random choice, possibly more than once and (b) prevention of Sybil attack by cost of identity creation.
Would you not agree that this has all been covered in posts 65 and 67-71?

I think your proposed solutions are really very good and I hope this will work. I am just comparing the options which you (and dansmith) already suggested earlier and at the moment I would conclude that it is much better to only record my banking session in the case of a dispute. And I see this only if the gateway is another user, because then nobody has to be online at the same time. Otherwise it would get really hard for some parties to proof that the gateway was online or was offline and if the connection was possible or was not possible because of some network failure or whatever. If the gateway is a party which is involved in the trade, it could get very hard to proof anything. If the gateway is choosen randomly at the time when it is needed, then you can proof something at all times independent from the other party.
105  Bitcoin / Project Development / Re: BitShare Economic Theory and 10 BTC Bounty to prove it wrong. on: May 29, 2013, 07:22:42 PM
Just for the record, I am not the only one who is unconvinced by your argument.   Will everyone who thinks this could still work please affirm their belief that it hasn't been proven unworkable.

I'm still not convinced by either side.
As you can see from my earlier posts I was first also very skeptical about it, because bytemaster used circular reasoning when he says that the price will be parity.

But still I also haven't seen a proof that it will not work. For example, it is not enough to say that the fiat price cannot enter the system because

no fiat data can reliably enter the system, or so it seems to me.

This has been stated several times, but it is not true. You underestimate the psychology of all market participants. Actually fiat data could enter the system through all parties which are trading between real USD, bitshares and crypto-USD.

Here is an illustration of how it might work, just by psychology:
Let's compare it to bitcoins. The supply of bitcoins is exactly determined. Therefore the bitcoin-USD exchange rate is very volatile because the demand is always changing according to good or bad news about bitcoins.
In contrast, now lets look at the supply of crypto-USD. The supply is floating and constantly changing according to the decisions of all market-participants (going short or long).
Nobody so far has stated exactly if the exchange rate will definitely go up or go down. So nobody knows exactly if it will go up or down. Therefore we could assume the following:
A) 40% of all market-participants think the exhange rate between crypto-USD to fiat-USD will go up
B) 40% of all market-participants think the exhange rate between crypto-USD to fiat-USD will go down
C) 20% believe that the concept of bitshares will work and therefore they think that crypto-USD will track fiat-USD

So 40% will go long, 40% will go short and 20% will go short or long depending on if the price is below or above parity.
Therefore the 20% of all market participants are enough to drive the market to parity.
106  Bitcoin / Project Development / Re: BitShare Economic Theory and 10 BTC Bounty to prove it wrong. on: May 29, 2013, 05:50:23 PM
no fiat data can reliably enter the system, or so it seems to me.

This has been stated several times, but it is not true. You underestimate the psychology of all market participants. Actually fiat data could enter the system through all parties which are trading between real USD, bitshares and crypto-USD.

Here is an illustration of how it might work, just by psychology:
Let's compare it to bitcoins. The supply of bitcoins is exactly determined. Therefore the bitcoin-USD exchange rate is very volatile because the demand is always changing according to good or bad news about bitcoins.
In contrast, now lets look at the supply of crypto-USD. The supply is floating and constantly changing according to the decisions of all market-participants (going short or long).
Nobody so far has stated exactly if the exchange rate will definitely go up or go down. So nobody knows exactly if it will go up or down. Therefore we could assume the following:
A) 40% of all market-participants think the exhange rate between crypto-USD to fiat-USD will go up
B) 40% of all market-participants think the exhange rate between crypto-USD to fiat-USD will go down
C) 20% believe that the concept of bitshares will work and therefore they think that crypto-USD will track fiat-USD

So 40% will go long, 40% will go short and 20% will go short or long depending on if the price is below or above parity.
Therefore the 20% of all market participants are enough to drive the market to parity.
107  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 29, 2013, 03:20:21 PM
I am starting to think that to keep these things 'straight' we need a computer to track all of the orders and display in real time what all prices/interest rates are.

I am making too many math errors by hand to accurately play the market.

So I tell you all what, give me a day or 2 and I will get a simple web-app up that will allow us to experiment with the result.

I am thinking when you 'login' you get an account with 100 sUSD.
It allows you to place all of the orders and tracks all interest rates.

It will then automate the 'interest' process and you can watch your balances update.

We can then track each of our 'networths' in real time to see who is getting ahead and who is falling behind..


Yeah this is a much better idea.

I know you won't want to spend weeks developing the app but it would be nice if ....

  • enough data be kept so we have the option of seeing a 'replay' of the game - so as to examine the behaviour of different players - and how it affects the market
  • an API could be exposed so I could create a simple bot to try and win the game!

Also how do you plan on simulating the BS / USD market price ? It would be nice to see how the currency works in times of crazy volatility.

If you want a hand with development, I have some time available...



I could also help with development if needed (depending on which language you use).
Now I am really curious about the simulation and the resulting data. Hopefully it will help us to better understand the concept and maybe improve it if there are some weaknesses/flaws.

I have one question: Isn't there a problem to implement the closing of a short position in the blockchain? Let's look at our simulation so far and hypothetically continue it in a way that you want to redeem your short position:

1) Bytemaster minted 10 cUSD with 5.5 MortgagedBS for cUSD @ .55 BS
2) greBit minted 20 cUSD with 10.2 MortgagedBS for cUSD @ .51 BS
3) Bytemaster sold 10 cUSD to nomailing
4) Bytemaster buys 10 cUSD from greBit
5) Bytemaster redeems his short-position (minted 10 cUSD @ .55 BS) with the bought 10 cUSD from greBit (minted 10 cUSD @ .51 BS).

As I understand so far you would have to implement #5 somehow like this:
In the blockchain you would have to annotate the tx-out of your newly bought 10 cUSD as now having the native currency unit BS again. But the underlying value of the tx-out is 10x0.51 BS in comparison to the 10x0.55 BS, which you would like to receive. So you have to redistribute all tx-outs, which are annotated in cUSD, in the blockchain. Only if the blockchain somehow redistributes the tx-outs you can redeem your 5.5 MortgagedBS by reminting the bought cUSD to BS. Otherwise you would only get 5.1 BS back, because you bought cUSD which were minted at a different rate.

I am not familiar enough with all bitcoin internals to know if this is easy to implement... But, is my reasoning in the example above correct? Is this redistribution of MBS neccessary when you want to close your short position?
108  Bitcoin / Project Development / Re: SSL logs as proof of money transfer for p2p exchanges on: May 29, 2013, 02:27:48 PM
Enters the scheme where the user doesn't have to expose his bank credentials and doesn't have to use SSL re-negotiation.
(But what I'm proposing below adds an extra level of complexity).

A randomly selected gateway user comes into play. The payer who has possesion of the SSL key does his banking session by channeling traffic to the bank through/from the gateway user. When the payer in finished, what happens is:
1. The gateway user submits to the e.agent only those packets which the payer has designated. (Packets which don't contain sensitive info)
2. The payer submits to the e.agent his SSL key, so that the e.agent could decrypt packets which gateway user gave him

I would add SSL-renegotiation (as optional for the payer) to increase security. How could you really be 100% sure that the gateway and the escrow do not exchange more of your session-dump or your session-key? This doesn't look 100% secure, maybe just 99% secure without SSL-renegotiation.  So it's better for the payer to use SSL-renegotiation if his bank supports it. And many important websites seem to support renegotiation (e.g. paypal and large banks).

Probably the only reason why renegotiation is disabled on some websites is the security vulnerability (CVE-2009-3555). That many banks have it disabled is overkill, because there is a patch for OpenSSL to close this vulnerability. Maybe over time many websites will anyway update to the newer openSSL version and will enable SSL-renegotiation again.

Weaknesses:
1. the bank may frown upon the payer logging into his bank from random IPs. But we discussed this earlier and it seems not to be a serious weakness.  
2. The payer can flood the p2p pool from which the gateway users get selected by his accomplices. If the payer and gateway user are in cahoots, they can spoof the whole SSL session.
3. To mitigate #2, the gateway user should be the beneficiary of the payment. (The beneficiary has no interest to defraud himself), which leads to ...
4. If the beneficiary is the gateway user and over time has a lot of those who pay him, the bank will flag the beneficiary's IP because there will be many users of that bank logging into their accounts from the same IP.

The problem which you describe in #2 applies also to the selection of the escrow agent. How would you make sure that the escrow agent is really a third party and not in cahoots with either the seller or buyer? Probably by some mechanism to randomly choose the escrow. So if it works there, why not use the same mechanism for the gateway? So I would say your point #3 doesn't make sense, especially if you think about the problem that they both have to be online at the same time it is better to select a random user from the pool?

To make sure that all 4 parties (seller,buyer,escrow,gateway) are really different persons, it would even make more sense to link p2p-accounts to real-world-bank-accounts. This would reduce the risk that someone could flood the p2p pool, because nobody has arbitrary many bank accounts.
109  Bitcoin / Project Development / Re: SSL dumps as proof of money transfer for p2p echanges on: May 29, 2013, 02:03:10 PM
I have a new suggestion, melding together several of the ideas already mentioned:

Adam is going to pay Betty USD in return for Bitcoins.

1. Betty puts Bitcoins into escrow
2. The software starts a proxy server on Betty's machine for Adam
3. Adam connects to his internet banking via the proxy.

The proxy acts purely as a forwarding mechanism.
I am basing this on the description:
Quote
If you want to connect to an HTTPS website via an HTTP proxy, you need to use the CONNECT HTTP verb (because that's how a proxy works for HTTPS). In this case, the proxy server simply connects to the target server and relays whatever is sent by the server back to the client's socket (and vice versa). There's no caching involved in this case (but you might be able to log the hosts you're connecting to).
here: http://stackoverflow.com/questions/3118602/convert-http-proxy-to-https-proxy-in-twisted/3186044#3186044
(the first answer)
I would *really* appreciate input from someone with good technical knowledge of SSLs and proxys to comment on feasibility of this.

4. Betty's proxy server logs the entire banking session in ENCRYPTED form. Also, Adam's software logs the whole session too, in unencrypted form.
5. If the wire transfer is successful, everyone is happy, no need to do more. If Betty disputes that the wire is received, then:
6. Escrow agent is called in. Escrow agent requests Adam to identify from his logs which pages he would like to provide to agent as proof that he did carry out the wire transfer.
7. Escrow agent requests those specific pages (which remember are still encrypted) from Betty.
8. Escrow agent requests master secret key from Adam
9. Escrow agent can decrypt the specific intended pages and verify that the wire was sent.

Plus points about this approach:
*As long as both sides have the necessary software installed, then if the transaction goes through normally, no one has to do actually *do* anything to ensure trust.
*Adam (the USD sender) has control over which HTML pages he sends to escrow in case of an audit. Normally it will be the last one or two pages of the banking session, and it may well be possible that he doesn't have to reveal any other transaction, or his balance.
*By using the counterparty as the "gateway", we remove the incentive for collusion. This is a brilliant idea and full credit to dansmith for it.

A problem with the approach to always have the proxy on the machine of the BTC-seller is that they might not be online at the same time. How could they agree to a specific online time? Should they specify this in their trade? In principle the BTC-buyer could just say that he couldn't do the transfer because the BTC-seller was always offline when he wanted to do it.
110  Bitcoin / Project Development / Re: BitShare Economic Theory and 10 BTC Bounty to prove it wrong. on: May 29, 2013, 11:24:27 AM
Points:
1. The strategy detailed above to wipe the value of the crypto-USD is ironclad.  
2. And so it the point that nobody would trust a currency where if the bottom bid got filled it would zero the currency value.

Isn't this the case also for all real-life currencies.
So I think you haven't presented a proof that the idea will not work.
111  Bitcoin / Project Development / Re: SSL logs as proof of money transfer for p2p exchanges on: May 29, 2013, 11:09:59 AM
(Other comments are for P2P exchange generally, I am thinking here more of my own plan as in https://bitcointalk.org/index.php?topic=210903.msg2210078#msg2210078):
But the general point of the Sybil attack applies to the role of escrow here. It's another good reason not to overemphasize reputation. Identities will be cheap to acquire here because they will be linked to bitcoin addresses. I wouldn't want to somehow make them artificially expensive. Users will have to enter bank account numbers too (encrypted I guess by default), but they don't necessarily have to use them so that doesn't help.

Off the cuff thought: we could retain the ability to create cheap addresses, and thus use the network to buy bitcoins for the first time, but limit escrow agency to members with non-zero bitcoin addresses (balance above X). This would prevent swamping the network. Then the escrow agent for any transaction would be chosen randomly from those slightly-higher-status users. And also, we could keep the option of a "second opinion" if an arbitration goes against you (but that's really off the top of my head, so if you don't like it, ignore it).

Indeed reputation should be in the system too. something like the OTC rating system. this would help to minimize disputes.
Why not link the p2p accounts (and the corresponding reputations) to the supplied real-world bank accounts? It would further minimize the number of disputes because nobody wants to risk that he can never use his bank account anymore in the p2p exchange. Is it possible to link p2p-account-reputations to real-world-bank-accounts without disclosing the bank-account-number to everyone? Maybe one could create a hash of the account-number, which then serves as the user-id in the p2p exchange?

Users will have to enter bank account numbers too (encrypted I guess by default), but they don't necessarily have to use them so that doesn't help.
Could you elaborate why this wouldn't help? I think if a user always trades using his paypal account, then he could build a good reputation by always using this exact paypal account. Consider he has a good reputation after some time, then he wouldn't want to fraud with this account? If you go further, a user might be able to link his paypal and bank-account and p2p-account all together to even get a higher reputation. And when he once linked them, then it's not possible to delink them anymore because everyone knows that these accounts belong to the same real-world person...
112  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 10:55:28 PM
greBit and nomailing both 'lost' money (opportunity cost) on their cUSD holdings because they minted at an interest rate lower than the interest rate paid by holding BS and didn't sell their cUSD to anyone for real dollars....

why did a 'lost' money? In my opinion I get interest for my cUSD, which you issued to me @.55BS which is more than the current exchange rate. So I should have made a profit, or am I wrong?

in other words, I anticipated the rise of cUSD value...
113  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 10:44:31 PM
Buy 20 @ 0.51 BS  (nomailing)
Mint 20 cUSD (backed by max 0.51 mBS)
114  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 10:11:34 PM
Ok, because at the moment there are no sell order, I will try to make a profit by setting some high price:

Sell 10 cUSD @ 1 BS
115  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 10:02:23 PM
Guys, I am open to advice on how to clean up the transaction thread... to make it easier to understand the market...

I would suggest to format the mortgage as MBS instead of mBS so that there is no confusion with milliBS. *EDIT* or some other letter.
116  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 09:41:33 PM
Still not quite sure how I should formulate it, if I want to mint some cUSD to myself. I will try it like this:

I want to purchase 20 cUSD for 5 BS.
I want to mint 20 cUSD (backed by 5 BS) in response to the highest bid.
*EDIT* is it possible to add a limit to my second order?


So I will back 1 cUSD with 0.25 mBS, right?
(btw, please correct my balance: subtract the 10 sUSD that I paid to you for the 10 cUSD)
117  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 09:02:40 PM
nomailing:  thanks for joining.  As both of your offers involve sUSD they cannot go into the blockchain, so we will pretend they were posted on craigslist.

What you are really saying is that you want to buy crypto-USD provided its value is near par with sUSD.    The last trade established sUSD to be worth 0.6 BS, therefore a crypto-USD could be issued for 0.6 BS and have parity.   If you would like to purchase some crypto-USD, I will gladly mint some for you at 0.55 BS.



ahh Ok, thanks.
I will accept that. So I pay you 10sUSD for 10 cryptoUSD (minted at 0.55 BS).
118  Bitcoin / Project Development / Re: BitShare Simulation Game Discussion (theory / economics in old thread) on: May 28, 2013, 08:47:57 PM
nice. I also want to participate. I hope your concept will work out although everyone is quite skeptical about it Smiley

I want to purchase 100 BitShares for 60 simulated USD, send BitShares to address nomailing1.
I want to purchase 10 Crypto-USD for 10 simulated USD if on average 1 Crypto-USD is backed by at least 0.9 BitShare. send CryptoUSD to address nomailing1.

I assume I can add this condition in my second order to be sure that the crypto-USD is backed by enough bitshares, right?
119  Bitcoin / Project Development / Re: Help Wanted $20,000+ Job creating Distributed Blockchain-based Exchange on: May 27, 2013, 10:34:57 AM
I think you misunderstand the nature of motive 2.  Someone who wants to convert crypto-USD to USD is doing so because they *FEAR* that crypto-USD will fall in value.  Therefore, they become SELLERS of crypto-USD which pushes the price of crypto-USD down.

But your assumtion that they *FEAR* that crypto-USD will fall in value is based on the assumption that they assume that the price will reach parity in the future. You haven't proven that this is the case.

For example you could do the same reasoning for BTC by just renaming it to crypto-USD. Just by naming it USD you could argue that people want to sell it for paper-USD if the price is 101$. But nobody can guaranty that the price will be on parity. In reality the price could diverge to some arbitrary number (like with the BTC-USD exchange rate). So I still think that you use circular reasoning... But probably I just miss some important point... Would be nice if you could point me to the correct reasoning if I made an error. thanks a lot..

@bytemaster you still haven't replied to my answer above. So I assume we are still on a different level. Maybe I still miss some important point, or you are still reliying on circular reasoning?!
I will try to clarify what I mean, so that we can maybe come to the same conclusions...

You say:
Also, if the price of crypto-USD is above face value then that effectively means they can make a profit by selling 100 crypto-USD for 101 paper-USD assuming they bought 100-crypto USD for $99 paper-USD the last time their was an imbalance of withdrawals and deposits.

But your assumption that "they can make a profit by selling 100 crypto-USD for 101 paper-USD" is solely based on the assumption that the exchange rate between crypto-USD and fiat-USD actually IS on average 1:1. So it is a circular argument.

So, I just want to point out here, that what you say in the white paper, is not a proof that the price will be parity (on average), because in your reasoning you use the assumption that the price is on parity on average. Do you see the point, and could you agree to this?

If that is the case, then maybe we could come to the following conclusion, which is what I understand from your reasoning: the exchange-rate between fiat-USD and crypto-USD will be 1 on average IF enough people think that the exchange-rate between fiat-USD and crypto-USD will be 1 on average. So although this IS circular reasoning, the idea might still work?! But it is no proof that it will work.
120  Bitcoin / Project Development / Re: Help Wanted $20,000+ Job creating Distributed Blockchain-based Exchange on: May 26, 2013, 05:03:14 PM
I think you misunderstand the nature of motive 2.  Someone who wants to convert crypto-USD to USD is doing so because they *FEAR* that crypto-USD will fall in value.  Therefore, they become SELLERS of crypto-USD which pushes the price of crypto-USD down. 

But your assumtion that they *FEAR* that crypto-USD will fall in value is based on the assumption that they assume that the price will reach parity in the future. You haven't proven that this is the case.

For example you could do the same reasoning for BTC by just renaming it to crypto-USD. Just by naming it USD you could argue that people want to sell it for paper-USD if the price is 101$. But nobody can guaranty that the price will be on parity. In reality the price could diverge to some arbitrary number (like with the BTC-USD exchange rate). So I still think that you use circular reasoning... But probably I just miss some important point... Would be nice if you could point me to the correct reasoning if I made an error. thanks a lot..
Pages: « 1 2 3 4 5 [6] 7 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!