Bitcoin Forum
June 19, 2024, 11:39:06 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 [93] 94 95 96 97 98 99 100 »
1841  Other / Off-topic / Re: ... like home on: March 19, 2011, 01:32:18 PM
You don't think repairing will also become automated?
1842  Bitcoin / Bitcoin Discussion / Re: Idea for increasing privacy in trasanctions: Onion Routing+SwarmMasking Payments on: March 19, 2011, 01:30:02 PM
How would they be able to transfer the money to the next hop without being capable of spending them?
1843  Other / Off-topic / ... like home on: March 18, 2011, 10:29:54 PM
We are on our way to having universal fabricators on each home, and at some point, after the economy shifted the focus to raw materials and services, it might get so easy and cheap to make your own automatons that there will be almost no job for humans while at the sametime making things becomes extreelly cheap and easy for everyone.


I made this thread 'cause i would like to ask you how long do you think it will take before we reach the point when everyone will have at least one unifab, and how long (if ever) untill we reach the utopia-like stage, where even aquicring material to use with our personal synthetizers costs almost nothing?
1844  Bitcoin / Bitcoin Discussion / Idea for increasing privacy in trasanctions: Onion Routing+SwarmMasking Payments on: March 18, 2011, 10:14:25 PM
In some cases it can be possible to analyze the blockchain and trace the moneyflow; what if the final target of a a transfer got encoded like the destination on onion routing,  each hop in the path only decryptable by the previous hop, each hop peeling away one layer (and for increased security, everynow and then adding a hop or two in the sequence, but less often than the "package" changes hops, otherwise it will never reach the final goal), and with the client relaying the onion routed trasfers whenever it gets one.



Obviouslly there is the risk unscrupulouslly coded clients could choose to not relay transfers and keep the money, for dealing with that, one way could be a distributed database of addresses and their respective reliability, whenever the netowrk acknoledges an address has received and sent a or'red package it's reliability goes up, and whenever it doesn't the reliability goes down (the final transfer wouldn't be considered onion routed, it would not have further hop payload; clients that send the initial transfer would create the path using random addresses found in the distributed database that got reliability above a given threshold (asking for a bigger threshold would likelly increase the difficulty in find a big number of nodes, and might also make the whole process take longer if too many people are using the same intermediaries, but going with the threshold set too low increases the odds the money will get lost before reaching the target. Solving conflicts when the database disagrees between peers would work kinda like chainsplits are delt with, the more peers agree with one version the more that version can be relied on (and perhaps whenever a client gets one version significantly more unreliable than others it would analyze the blockchain and calculate it's own database checking what matches and what is differerhaps an opptmization would be to onlyr verify the parts that don't match between the different versions of the database seen.

An additional benefit for running nodes could be a onion routing fee, whenever a client peels a layer and passes it on it could receive a percetntage or fixed value comming out from the money transfered, the reliability algorithm would need to take in consideration how big the fee offered was defined in the transactions and how much each node took from the package, raking negativelly those that take more than what was offered; the fee would have to stay outside, or be included in each layer so all clients can see it without needing to be able to decrypt the whole onion. And of course, running an exit node would provide you with plausible deniability for any payment you make since those payments could actually have been done by someone else and just existed the onion router network by our node.


Actually, forget the bit about nodes randomlly adding more hops, that would allow cheating (perhaps some sort of signing of each layer would be necessary so only the original sender can define the hops); though either way the transaction would get lost)





Of course this would mutiply the time for a payment to reach it's intended destination, but i wouldn't doubt some people would be willing to wait a little longer inorder to get more privacy. 


What do you think?
1845  Bitcoin / Project Development / Re: About all the posts from Chinese with poor Engrish on: March 18, 2011, 09:32:15 PM
...

@Nefario, some feedback for next time:
Have them make a business plan in advance, so that they know what they will be selling/doing to make money. Now, they are mostly asking the market to come up with ideas of  what their business should be. In the big "western" world this would look stupid and they would fail. ...


Actually, a company that lets the customer come up with what they want to pay for doesn't sound like a bad idea at all. Eventually they would specialize untill growing again adding more people to other things, but from the start they would already have a market without even having to experiment with selling different things to see what people would pay for.
1846  Economy / Economics / Re: Bitcoin: Disaster Proof? on: March 18, 2011, 09:00:24 PM
I'm curious regarding whether the Moon would be under the coverage of the Internet all the time or if during periods of it's orbit and Earth's rotation (like when it's going over the ocean) it would stay "offline".
1847  Bitcoin / Bitcoin Discussion / Re: Printing bitcoins, an implementation on: March 18, 2011, 08:43:55 PM
Does it got error correction, like, could i replace a big part of it with an image of my choice and still have it work like how happens with QR code? And is it at least as easy to dentify and read by devices as QR code?
1848  Bitcoin / Bitcoin Discussion / Re: the "little toe" crypto currency on: March 17, 2011, 08:12:47 AM
1. cut toes
2. sprinkle pig's bladder dust
3. ???
4. PROFIT!!!!!!!!!
1849  Bitcoin / Bitcoin Discussion / Re: Bitcoins in space on: March 17, 2011, 08:03:47 AM
Do they got actual internet on the ISS or do they use only specialized communication means (plus regular radio) ?
1850  Economy / Economics / Re: Bitcoin: Disaster Proof? on: March 17, 2011, 08:01:16 AM
Would Luna based machines talk directly with machines on Terra's ground or would it talk with Terran satelites, or even it's own satelite network that in turn would talk with Terran satelites?
1851  Bitcoin / Bitcoin Discussion / Re: What would Bitcoin for wetware be like? on: March 16, 2011, 06:45:32 AM
Don' forget we need a system with tweakable difficulty so the distributed system would automaticly adapt itself to adjust for changes in the ammount of miners, new block solving means (depending on how block solving works, someone might figure out some new algorithm to make it more easilly solvable, even for things done by humans) etc
1852  Bitcoin / Development & Technical Discussion / Re: A full shell script implementation of bitcoin ? on: March 16, 2011, 06:37:07 AM
how far are we from a total implementation?
1853  Bitcoin / Bitcoin Discussion / What would Bitcoin for wetware be like? on: March 16, 2011, 05:04:34 AM
How different would Bitcoin be if it was designed to be handled completly by humans?

Can the proof of work dificulty be tweaked to an extreme such that regular people with spare time could solve blocks with pen and paper? How would the network work with people exchanging and copying sheets of paper? Would it be possible to get reliable confirmation of transfers in less than a day? What would need to be changed and what would work just the way it is?
1854  Economy / Marketplace / Re: BTC not permitted on eBay? on: March 16, 2011, 04:53:56 AM
Oh, i see
1855  Economy / Marketplace / Re: BTC not permitted on eBay? on: March 15, 2011, 11:16:20 AM
Could they do anything if you were selling an encrypted wallet file, to which the buyer would get the password/key for free after the purchase?
1856  Economy / Marketplace / Re: BitBet - gambling on upcoming events on: March 15, 2011, 11:06:17 AM
Nice to hear, thanx for the update
1857  Economy / Trading Discussion / Re: BitBet on: March 14, 2011, 03:38:02 PM
Regarding the odds calculation thing, isn't there an algorithm that is based on how much has been bet for and against?


Btw, instead of the betting service holding the money while the bet result isn't in yet, what if some escrow did it?
1858  Bitcoin / Bitcoin Discussion / Re: What Happens When Double Spending Occurs With USD??? on: March 14, 2011, 04:26:46 AM
Wasn't double spending one of the main causes banks needed to be rescued by the governament? (the bank lends 100 bucks to person A in the form of an redistributable IOU ticket, then they do the same with person B and person C; but then person A and person B go bankrupt and don't pay the bank back, now  the bank has spent 300 bucks but only really has 100 bucks to to pay the all the IOUs they distributed)
1859  Bitcoin / Bitcoin Discussion / Re: The Week In Bitcoin - Mar 7 through Mar 13, 2011 on: March 13, 2011, 05:45:59 PM
Is there a way i can get the weekly digest by email?
1860  Bitcoin / Bitcoin Discussion / Re: Can I be taxed? on: March 13, 2011, 05:12:56 PM

There's another one called CoinTumbler at the Onion address: http://lbrmvt4plqojaulx.onion/

Server Not Found error on the onion address.  Is that correct address?

Are you trying to access it thru TOR?
Pages: « 1 ... 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 [93] 94 95 96 97 98 99 100 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!