What would you do if a certain user, decides to send messages to himself. He makes a backup of his hard drive and stores 100gb worth of messages on the network.
The network does not store messages, only relay them. Nodes store messages that are relevant to them. Read notifications would be used as indicators of a message needing to be rebroadcast. I think there doesn't need to be any whitelisting actually! Just anti-DoS limitations per node. I am not too well versed on crypto, but I'm assuming that it's possible to encrypt a message so that it is rubbish to everyone else except to those with private keys to a specified list of public keys. |
|
|
|
|
Sent. Waiting for the PM.
|
|
|
|
One concern I have is with the 'whitelisting' you mention. Could this be used to for example prevent all messages from 'wikileaks' being relayed. Or perhaps a powerful adversary, could track the IP addresses of nodes that relay ''wikileaks' messages in an attempt to unmask the real identities of the communication participants. This is definitely a valid concern, however in practice I believe this will not happen as people can simply add nodse that do not cesnor messages. You are not limited to one node. If I wanted to send a message to Bob, I would prefer that my message, M, appear as random encrypted rubbish to all network participants except for Bob, who has the private key for decryption and is the only other person able to tell that author(M) = me
I think I would prefer alternative spam prevention techniques such as by introducing a cost to store a message on the network. The tradeoff of this is that nodes must store messages, and the system will no longer be free. People are happy to try out a new web app for free, but they will not want to pay. I believe the current system can be very anonymous with automatic identity generation. While your first message may tell people who you communicate with if you sent it to a publicly listed identity, the client by default may randomly send a bunch of messages to random public identities to mask this. |
|
|
|
Got 5000 satoshis  |
|
|
|
|
The cost would not be in actually trading on the exchanges but rather connections, media bias, regulatory actions, etc.
|
|
|
|
tried it yesterday, took me 5min to crack 2 promising vanity addresses. never ever use brainwallet. NEVER, if you're new to passwords.
Crack vanity addresses?   |
|
|
|
Try Inputs.io. It's instant, and you don't need to worry about double spending. https://inputs.ioNo fees. |
|
|
|
then how the hell do you keep track of it? bring me back to my original point about dht and datacentres. how are you going to keep track of which addresses are in use at any given time with out a block chain, or at least leveraging magnet links(dht) to a datacentre(s) with the current database of addresses/keys
also, i think you will need to address things like collision and error handling. really is a great idea though. i'm all ears
Track what? |
|
|
|
|
zero cause you won't be able to run unsigned code.
|
|
|
|
This is awesome - thanks so much! No longer will I have to wait or beg for new blocks on testnet. That also means I cannot procrastinate for 5 - 30 minutes through  .. |
|
|
|
Your efforts are turning Bitcoin into a centralized, debt and interest ridden cashless currency.
WTG !
HT :/
I think that's an exaggeration. |
|
|
|
So basically you want each new message between the two nodes to be sent to a newly generated address, right?
Yes. This is OK because it doesn't matter if there are 100 addresses or 10,000 - there is no blockchain. |
|
|
|
I also do that if I stick a Bitcoin address on my website or in my signature.
Not if you mix it  But anyway, I definitely agree with this point: PS. I'm not saying there isn't value to off-chain systems for a lot of use-cases, just that off-chain isn't the only way to do it, and has a lot of downsides. |
|
|
|
|
You need to fix your time zone:
"Submitted 8 hours ago by Anonymous"
It's off by 8 hours.
|
|
|
|
|
Also, how much bandwidth are you prepared for? What is your hotlinking policy?
|
|
|
|
imgur is harder to remember
I disagree. Think of smartphones, software keyboards, etc. If you do not have a .com domain, that is additional entropy people need to remember too. |
|
|
|
How this worksThis is a lowest unique bid auction. The person who places the lowest, but unique bid gets one Bitcoin. Bids must be in increments of 0.01 BTC (a bitcent). Example0.01 BTC: 3 bids, Alice, Bob and Charlie 0.02 BTC: 2 bids, Alice and Bob 0.03 BTC: no bids 0.04 BTC: 4 bids, Bob, Charlie, Daniel, Eve 0.05 BTC: 1 bid, Eve0.06 BTC: 2 bids, Bob, Eve Eve wins the auction and gets one Bitcoin. Multiple BidsTo reduce variance, it may not be a bad idea to place multiple bids on sequential (or not) price points. When does this end?7 days from this post. But can't others see all the bids?That's why this uses Inputs.io  To bid, send increments of 0.01 BTC to http://inputs.io/pay?to=gladoscc¬e=Lowest+Unique+Bid+Auction+Round+1
|
|
|
|
|
Qt should not allow bitcoin addresses as labels.
|
|
|
|
|
From your post history, you have purchased coins multiple times from btcQuick. Why not do that?
|
|
|
|
|
Show Posts
