Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6530. (Read 9723858 times)

full member
Activity: 168
Merit: 100
We need a big transaction like this in DRK to grab the attention of media. Anyone want to buy/sell a Bali villa?

http://www.nbcnews.com/tech/internet/500-000-bitcoin-just-bought-someone-villa-bali-n57211

start with a t-shirt

Ha, yeah a villa might be reaching but something substantial and across borders would be something to write about  Smiley
full member
Activity: 128
Merit: 100
We need a big transaction like this in DRK to grab the attention of media. Anyone want to buy/sell a Bali villa?

http://www.nbcnews.com/tech/internet/500-000-bitcoin-just-bought-someone-villa-bali-n57211

start with a t-shirt
full member
Activity: 168
Merit: 100
We need a big transaction like this in DRK to grab the attention of media. Anyone want to buy/sell a Bali villa?

http://www.nbcnews.com/tech/internet/500-000-bitcoin-just-bought-someone-villa-bali-n57211
legendary
Activity: 1708
Merit: 1049
If I'm not mistaken the feature regarding encrypted messages over the network was discussed in the early days of bitcoin development (not in the "adding noise to darksend" context). I do not remember what was the reason for not implementing it though. Priorities? Some kind of problem like bloating? It'd be interesting if some old-timer remembers what happened and why that feature got "stuck".

The messages would be a nice addition, but its not a high priority. It will take ALOT of testing to make sure someone cant put text in that would cause injection issues.

Why would we add messages to a crypto coin? Isn't bitmessage the perfect option for those who wish to send private messages?

I think the concept is about short messages attached to transactions (or transaction-less short messages for noise per the earlier poster).
full member
Activity: 176
Merit: 100
If I'm not mistaken the feature regarding encrypted messages over the network was discussed in the early days of bitcoin development (not in the "adding noise to darksend" context). I do not remember what was the reason for not implementing it though. Priorities? Some kind of problem like bloating? It'd be interesting if some old-timer remembers what happened and why that feature got "stuck".

The messages would be a nice addition, but its not a high priority. It will take ALOT of testing to make sure someone cant put text in that would cause injection issues.

Why would we add messages to a crypto coin? Isn't bitmessage the perfect option for those who wish to send private messages?
member
Activity: 84
Merit: 10
Darkcoin is LIVE on agx.io! Trade DRK/BTC for FREE during Beta. AGX is running a 50k NOBL deposit bonus for BTC deposits >.02 BTC through 03/23 11:59p UTC and enter to win an AMD Radeon R9 280x giveaway. Learn more about the promotion here: http://31.media.tumblr.com/787b05ed67a5db64ceecd90c75f529b0/tumblr_n2prr4jmrP1trlaa8o1_1280.png

- The Austin Global Team

Find us at:
agx.io
bitcointalk.org/index.php?topic=507474
bitcointalk handles: "agx.io," "AustinGlobal"
twitter.com/AustinGlobalX
austinglobal.tumblr.com
full member
Activity: 154
Merit: 100
If I'm not mistaken the feature regarding encrypted messages over the network was discussed in the early days of bitcoin development (not in the "adding noise to darksend" context). I do not remember what was the reason for not implementing it though. Priorities? Some kind of problem like bloating? It'd be interesting if some old-timer remembers what happened and why that feature got "stuck".

The messages would be a nice addition, but its not a high priority. It will take ALOT of testing to make sure someone cant put text in that would cause injection issues.
full member
Activity: 168
Merit: 100
Coinmine is creeping up again!



if you want to spread some hash around, try stratum+tcp://darkcoin.kicks-ass.net:7903

P2Pool node with only 0.5% fee (Hey, I gotta keep the lights on here!)
legendary
Activity: 1708
Merit: 1049
Quote
It didn't really get stuck, someone brought up the idea, everyone liked it, but at the time we wanted to concentrate on what was to become darksend.

Sorry if I wasn't clear, I meant that the idea was brought up a couple of years ago when Bitcoin (not Darkcoin) was in its first stages of development (so the question of why wasn't it implemented is for Bitcoin really in order that we can find the answer of why the Bitcoin devs didn't push it, did they have some issue or something?)
full member
Activity: 168
Merit: 100
I hear you... But I think that in this case, it could provide additional functionality without much overhead... I might be wrong, and I'm no programmer, either. But imagine the usefulness of being able to send a small note, a shipping address, a software key, etc. along with a darksend transaction. It would REALLY add to the usability as a medium of exchange.

InternetApe confirmed a few pages back they would like to enable sending messages and it's on the list for future features.

Aha! You're right... I"m going to keep pondering it in case any of these ideas are helpful...
full member
Activity: 280
Merit: 100
The Future Of Work
If I'm not mistaken the feature regarding encrypted messages over the network was discussed in the early days of bitcoin development (not in the "adding noise to darksend" context). I do not remember what was the reason for not implementing it though. Priorities? Some kind of problem like bloating? It'd be interesting if some old-timer remembers what happened and why that feature got "stuck".

It didn't really get stuck, someone brought up the idea, everyone liked it, but at the time we wanted to concentrate on what was to become darksend.  The other things that have been done for the coin besides, came from immediate need (rework of the rewards(was too harsh), KGW then DGW).  Aside from those, the concentration has always been to get Darksend out of Beta and into DarkCoin ASAP while making sure it's completely solid.

We have Evan for at least 2 years, as he's dedicated 100% of his time for the next two years, LOL, and we'll hold him to it Wink  So I'm sure, with the speed and skill he brings to this coin, we'll have all kinds of amazing features by the time he has finished!

Oh, sorry, I see you were talking about bitcoin!  Nevermind, LOL
legendary
Activity: 1708
Merit: 1049
If I'm not mistaken the feature regarding encrypted messages over the network was discussed in the early days of bitcoin development (not in the "adding noise to darksend" context). I do not remember what was the reason for not implementing it though. Priorities? Some kind of problem like bloating? It'd be interesting if some old-timer remembers what happened and why that feature got "stuck".
full member
Activity: 280
Merit: 100
The Future Of Work
It's not any less trackable to 'the same' user if the change goes to a throw away address to original wallet or secondary wallet, plus that just complicates things to where it isn't usable.
Whenever a change address from a darksend is used in a transaction with an address existing before the darksend there could potentially be a privacy breach. In the current implamentation, the wallet constructs transactions from any of the addresses it has control over, so this could happen on any transaction if the wallet keeps its own change. By sending the change to a completely different wallet, there is no chance for those addresses to get mixed together.

I don't see why this would be necessary as the change is returned with a stealth address?
sr. member
Activity: 322
Merit: 250


I hear you... But I think that in this case, it could provide additional functionality without much overhead... I might be wrong, and I'm no programmer, either. But imagine the usefulness of being able to send a small note, a shipping address, a software key, etc. along with a darksend transaction. It would REALLY add to the usability as a medium of exchange.

Id love a feature like this too but the very last thing we want is something broken.
Also my thought about blockchain size, what in 10 years from now? sure hardware gets cheaper and more effective but look at bitcoin blockchain.
Id be very much interested if we can shrink the actual blockchain size while maintaining the level of anonymity and security.
hero member
Activity: 1302
Merit: 502
I hear you... But I think that in this case, it could provide additional functionality without much overhead... I might be wrong, and I'm no programmer, either. But imagine the usefulness of being able to send a small note, a shipping address, a software key, etc. along with a darksend transaction. It would REALLY add to the usability as a medium of exchange.

InternetApe confirmed a few pages back they would like to enable sending messages and it's on the list for future features.
full member
Activity: 168
Merit: 100
Remember that idea about being able to send a short message via darksend? I was thinking about it again, and it occurred to me that it could work this way:

Each transaction that is denominated also contains an encrypted "message" string. If a "real" message is being sent, a fee (whatever is reasonable) is deducted from the wallet, and included in the denominated sums <- length to be determined by reasonable block size, but I'm thinking something around twitter-sized. We don't want to bloat the blockchain

Each message transaction that contains a message and is not really part of any amount to be distributed has a certain (random) amount removed and added to the block reward. The remaining amount is then sent to the intended recipient. All blocks coming form darksend have encrypted messages strings, but only some of the strings  have real messages. The real messages can only be decrypted by the recipient after arriving, perhaps using one of the wallet's addresses as a key.

Encryption should be no problem because the network is hashing encryption anyway - why not use some of it?

If every transaction (at least every Darksend transaction) has an message string attached, it would be impossible to tell which were real or not. It would also add additional, non-transactions to Darksend, which would further obfuscate the in <> out of the pool


The idea is nice BUT , KISS , what first comes to my mind is anything that flows in the blockchain makes it bigger, the second thing is every part we add might be attackable. Im not a programmer, just my common sense.

I hear you... But I think that in this case, it could provide additional functionality without much overhead... I might be wrong, and I'm no programmer, either. But imagine the usefulness of being able to send a small note, a shipping address, a software key, etc. along with a darksend transaction. It would REALLY add to the usability as a medium of exchange.
sr. member
Activity: 322
Merit: 250
Remember that idea about being able to send a short message via darksend? I was thinking about it again, and it occurred to me that it could work this way:

Each transaction that is denominated also contains an encrypted "message" string. If a "real" message is being sent, a fee (whatever is reasonable) is deducted from the wallet, and included in the denominated sums <- length to be determined by reasonable block size, but I'm thinking something around twitter-sized. We don't want to bloat the blockchain

Each message transaction that contains a message and is not really part of any amount to be distributed has a certain (random) amount removed and added to the block reward. The remaining amount is then sent to the intended recipient. All blocks coming form darksend have encrypted messages strings, but only some of the strings  have real messages. The real messages can only be decrypted by the recipient after arriving, perhaps using one of the wallet's addresses as a key.

Encryption should be no problem because the network is hashing encryption anyway - why not use some of it?

If every transaction (at least every Darksend transaction) has an message string attached, it would be impossible to tell which were real or not. It would also add additional, non-transactions to Darksend, which would further obfuscate the in <> out of the pool


The idea is nice BUT , KISS , what first comes to my mind is anything that flows in the blockchain makes it bigger, the second thing is every part we add might be attackable. Im not a programmer, just my common sense.
full member
Activity: 196
Merit: 100

http://darkcoin.mine.nu/poolhash.html

This is pool hashrate (sum of pool's hash. coinmine, such, lottery, mininghub, official, p2pool, cpupool)

update : 10 min.
recent block : when block found.



Very good job man!
full member
Activity: 168
Merit: 100
Remember that idea about being able to send a short message via darksend? I was thinking about it again, and it occurred to me that it could work this way:

Each transaction that is denominated also contains an encrypted "message" string. If a "real" message is being sent, a fee (whatever is reasonable) is deducted from the wallet, and included in the denominated sums <- length to be determined by reasonable block size, but I'm thinking something around twitter-sized. We don't want to bloat the blockchain

Each message transaction that contains a message and is not really part of any amount to be distributed has a certain (random) amount removed and added to the block reward. The remaining amount is then sent to the intended recipient. All blocks coming form darksend have encrypted messages strings, but only some of the strings  have real messages. The real messages can only be decrypted by the recipient after arriving, perhaps using one of the wallet's addresses as a key.

Encryption should be no problem because the network is hashing encryption anyway - why not use some of it?

If every transaction (at least every Darksend transaction) has an message string attached, it would be impossible to tell which were real or not. It would also add additional, non-transactions to Darksend, which would further obfuscate the in <> out of the pool
full member
Activity: 168
Merit: 100

http://darkcoin.mine.nu/poolhash.html

This is pool hashrate (sum of pool's hash. coinmine, such, lottery, mininghub, official, p2pool, cpupool)

update : 10 min.
recent block : when block found.



Chaeplin, do you have a DRK address for tips? You really deserve some for all the work you've put in.
Jump to: