why it's the best coin ? 
i don't know, someone said drk instaminded
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5079. (Read 9723858 times)
June 24, 2014, 04:14:01 AM
i don't know, someone said drk instaminded
June 24, 2014, 04:09:28 AM
why it's the best coin ?
June 24, 2014, 04:06:14 AM
Right now ,tt's hard to say where the drk going to be
June 24, 2014, 03:04:12 AM
How old do I have to be so I have to generate the money back?
How many Darkcoins can you mine approximate per day with this rig ( 4 x R9 270 )? I belive not enough and dont forget the costs of electricity!
I dont run 270s myself but the newest sgminers seem to pull ~2.1mh (YMMV) so @8.4mh you'd pull in approx 0.20291872 drk per
day at the current diff (4163.71557343).
So using those number (which will change constantly but to give you an idea) would set you @ 985.61 days to make the 200 dark back.
June 24, 2014, 02:12:31 AM
I could sell as well, but shipping for me would be too expensive.
June 24, 2014, 02:10:02 AM
How old do I have to be so I have to generate the money back?
How many Darkcoins can you mine approximate per day with this rig ( 4 x R9 270 )? I belive not enough and dont forget the costs of electricity!
June 24, 2014, 01:49:54 AM
Yes, I understand this. But if I have for example 110 DRK in my wallet (one address) will the "denomination" create transaction that will send 100 DRK to new address and then this new address will go thru the pool?
Currently if you want to send say 15 coins for example - 10 coins will go to an address you own, 100 coins will enter the pool, 85 of those coins will come back as change.
Eventually Darksend will work slightly differently, the entire 115 coins enter the pool, you will receive 100 coins back as change at many different addresses in various denominations.
June 24, 2014, 01:47:17 AM
Yes, I understand this. But if I have for example 110 DRK in my wallet (one address) will the "denomination" create transaction that will send 100 DRK to new address and then this new address will go thru the pool?
Currently if you want to send say 15 coins for example - 10 coins will go to an address you own, 100 coins will enter the pool, 85 of those coins will come back as change.
Eventually Darksend will work slightly differently, the entire 115 coins enter the pool, you will receive 100 coins back as change at many different addresses in various denominations.
Thank you. Can the community post updated whitepaper and graphics on the first page of this thread? According to your answer it is obsolete and people may make wrong conclusions about DarkSend.
June 24, 2014, 01:36:01 AM
Ok, thanks, but I don't see any "denomination" happening in these examples?
See the inputs of 10:
http://explorer.darkcoin.io/tx/56b3b95b76995d3e4d3107cf753c8496493010f625fc04d971e9262d74e6a5a5
June 24, 2014, 12:58:14 AM
Yes, I understand this. But if I have for example 110 DRK in my wallet (one address) will the "denomination" create transaction that will send 100 DRK to new address and then this new address will go thru the pool?
Currently if you want to send say 15 coins for example - 10 coins will go to an address you own, 100 coins will enter the pool, 85 of those coins will come back as change.
Eventually Darksend will work slightly differently, the entire 115 coins enter the pool, you will receive 100 coins back as change at many different addresses in various denominations.
June 24, 2014, 12:54:38 AM
One technical question about DarkSend.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
[...]
Thanks for the questions. It does seem like you're missing something. Although, it might not be your fault. The whitepaper is definitely out of date. We've done a lot of work at tweaking the trust model so that it can't be exploited. I'll try to explain how it works briefly, then hopefully if I get time I can revisit the whitepaper soon.
- Masternodes don't have any power over the transactions. They just coordinate the signing. All parties must sign in order for the transaction to be valid. So there's no way to cheat and take the money.
- Users submit collateral. At a later phase if a user doesn't provide the signature as agreed, the transaction will fail. Without colateral this could be done over and over bringing the system to a halt.
- Masternodes have the ability to take the collateral transaction if they wish, but it's paid to the bounty fund. So it doesn't benefit them, it just benefits the community. This removed the incentive to cheat and take the money.
There's no relying on pools at all anymore. Payments to masternodes are done with a voting system embedded into the blockchain. It would take 51% of the mining power to pay the wrong masternode, or another party (because the last few miners to solve blocks must agree on who should be paid)
Transaction currently require 3 parties to be created, so there's a short wait. There are no fake transactions to make that quicker, although this could be done. There's usually 5 or so transaction per 2.5 minutes, so the network should be able to function pretty efficiently under these requirements.
Hoping that helps . Thanks,
Evan
Ok, thanks, but I don't see any "denomination" happening in these examples?
The amount sent, depending on its value, go thru a pool of 10, 100, 1000 etc. DRK.
It's worth mentioning that Evan decided to scrap denominated pools because of various issues (needing more coins than you want to send, "dirty" addresses that result from the splitting off of a denominated amount, etc). The plan is to allow inputs of any size into a single pool (with a minimum resolution of .1 DRK), the change addresses will be denominated and sent back to several different addresses. Denominated change addresses will come in RC4, pool size change will happen in either RC4 or maybe later, not sure.
June 24, 2014, 12:27:33 AM
dark will be good in the future.
June 23, 2014, 08:36:37 PM
Help test the RC3 prelaunch!
https://darkcointalk.org/threads/rc3-prelaunch-testing.1523/
https://darkcointalk.org/threads/rc3-prelaunch-testing.1523/
current test pool hashrates :
Pool 1 : Mpos + Stratum: http://ec2-54-198-19-83.compute-1.amazonaws.com
Pool hashrate 47,7 MH
Pool 2 : P2Pool: http://54.213.244.5:18998/static/
Pool hashrate : 8.96 MH
Pool 3 : NOMP: http://54.183.73.24/
Pool hashrate : 6.55 MH
lets get more hashpower to these test pools
qwizzie
Just read here. Another 5MH frome China will be showed on the testnet when i get home.
June 23, 2014, 08:03:12 PM
June 23, 2014, 07:53:59 PM
I'm very interested in learning more aboot darksend
Posted From bitcointalk.org Android App
Posted From bitcointalk.org Android App
June 23, 2014, 07:50:49 PM
One technical question about DarkSend.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
[...]
Thanks for the questions. It does seem like you're missing something. Although, it might not be your fault. The whitepaper is definitely out of date. We've done a lot of work at tweaking the trust model so that it can't be exploited. I'll try to explain how it works briefly, then hopefully if I get time I can revisit the whitepaper soon.
- Masternodes don't have any power over the transactions. They just coordinate the signing. All parties must sign in order for the transaction to be valid. So there's no way to cheat and take the money.
- Users submit collateral. At a later phase if a user doesn't provide the signature as agreed, the transaction will fail. Without colateral this could be done over and over bringing the system to a halt.
- Masternodes have the ability to take the collateral transaction if they wish, but it's paid to the bounty fund. So it doesn't benefit them, it just benefits the community. This removed the incentive to cheat and take the money.
There's no relying on pools at all anymore. Payments to masternodes are done with a voting system embedded into the blockchain. It would take 51% of the mining power to pay the wrong masternode, or another party (because the last few miners to solve blocks must agree on who should be paid)
Transaction currently require 3 parties to be created, so there's a short wait. There are no fake transactions to make that quicker, although this could be done. There's usually 5 or so transaction per 2.5 minutes, so the network should be able to function pretty efficiently under these requirements.
Hoping that helps . Thanks,
Evan
Ok, thanks, but I don't see any "denomination" happening in these examples?
The amount sent, depending on its value, go thru a pool of 10, 100, 1000 etc. DRK.
Yes, I understand this. But if I have for example 110 DRK in my wallet (one address) will the "denomination" create transaction that will send 100 DRK to new address and then this new address will go thru the pool?
June 23, 2014, 07:45:34 PM
One technical question about DarkSend.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
[...]
Thanks for the questions. It does seem like you're missing something. Although, it might not be your fault. The whitepaper is definitely out of date. We've done a lot of work at tweaking the trust model so that it can't be exploited. I'll try to explain how it works briefly, then hopefully if I get time I can revisit the whitepaper soon.
- Masternodes don't have any power over the transactions. They just coordinate the signing. All parties must sign in order for the transaction to be valid. So there's no way to cheat and take the money.
- Users submit collateral. At a later phase if a user doesn't provide the signature as agreed, the transaction will fail. Without colateral this could be done over and over bringing the system to a halt.
- Masternodes have the ability to take the collateral transaction if they wish, but it's paid to the bounty fund. So it doesn't benefit them, it just benefits the community. This removed the incentive to cheat and take the money.
There's no relying on pools at all anymore. Payments to masternodes are done with a voting system embedded into the blockchain. It would take 51% of the mining power to pay the wrong masternode, or another party (because the last few miners to solve blocks must agree on who should be paid)
Transaction currently require 3 parties to be created, so there's a short wait. There are no fake transactions to make that quicker, although this could be done. There's usually 5 or so transaction per 2.5 minutes, so the network should be able to function pretty efficiently under these requirements.
Hoping that helps . Thanks,
Evan
Ok, thanks, but I don't see any "denomination" happening in these examples?
The amount sent, depending on its value, go thru a pool of 10, 100, 1000 etc. DRK.
June 23, 2014, 07:34:13 PM
One technical question about DarkSend.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
[...]
Thanks for the questions. It does seem like you're missing something. Although, it might not be your fault. The whitepaper is definitely out of date. We've done a lot of work at tweaking the trust model so that it can't be exploited. I'll try to explain how it works briefly, then hopefully if I get time I can revisit the whitepaper soon.
- Masternodes don't have any power over the transactions. They just coordinate the signing. All parties must sign in order for the transaction to be valid. So there's no way to cheat and take the money.
- Users submit collateral. At a later phase if a user doesn't provide the signature as agreed, the transaction will fail. Without colateral this could be done over and over bringing the system to a halt.
- Masternodes have the ability to take the collateral transaction if they wish, but it's paid to the bounty fund. So it doesn't benefit them, it just benefits the community. This removed the incentive to cheat and take the money.
There's no relying on pools at all anymore. Payments to masternodes are done with a voting system embedded into the blockchain. It would take 51% of the mining power to pay the wrong masternode, or another party (because the last few miners to solve blocks must agree on who should be paid)
Transaction currently require 3 parties to be created, so there's a short wait. There are no fake transactions to make that quicker, although this could be done. There's usually 5 or so transaction per 2.5 minutes, so the network should be able to function pretty efficiently under these requirements.
Hoping that helps . Thanks,
Evan
Ok, thanks, but I don't see any "denomination" happening in these examples?
June 23, 2014, 07:17:03 PM
One technical question about DarkSend.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
Let's say that I have 110 DRK in one address and I want to pay 30 DRK to another user using DarkSend.
DarkSend does something called "denomination". What does this mean? That it will send first 100 DRK to another address and then include these 100 DRK in DarkSend pool from this address?
Is this just this one transaction (in this example) or maybe denomination does also something else so that the original address (with 110 DRK at the beginning) is somehow obfuscated?
Thanks.
[...]
Thanks for the questions. It does seem like you're missing something. Although, it might not be your fault. The whitepaper is definitely out of date. We've done a lot of work at tweaking the trust model so that it can't be exploited. I'll try to explain how it works briefly, then hopefully if I get time I can revisit the whitepaper soon.
- Masternodes don't have any power over the transactions. They just coordinate the signing. All parties must sign in order for the transaction to be valid. So there's no way to cheat and take the money.
- Users submit collateral. At a later phase if a user doesn't provide the signature as agreed, the transaction will fail. Without colateral this could be done over and over bringing the system to a halt.
- Masternodes have the ability to take the collateral transaction if they wish, but it's paid to the bounty fund. So it doesn't benefit them, it just benefits the community. This removed the incentive to cheat and take the money.
There's no relying on pools at all anymore. Payments to masternodes are done with a voting system embedded into the blockchain. It would take 51% of the mining power to pay the wrong masternode, or another party (because the last few miners to solve blocks must agree on who should be paid)
Transaction currently require 3 parties to be created, so there's a short wait. There are no fake transactions to make that quicker, although this could be done. There's usually 5 or so transaction per 2.5 minutes, so the network should be able to function pretty efficiently under these requirements.
Hoping that helps . Thanks,
Evan
June 23, 2014, 07:15:53 PM
please stop feedin the troll , i think hes a sleep now so last 2 pages have been quiet. this forum is full of smart people , id rather listen to them than have 5pages of the same boring fud over n over. its obvious he wants cheap drk thats why he wasting so much time on this forum.
Time to help on testnet, 4mhs, on the way
Time to help on testnet, 4mhs, on the way
Jump to: