BTCD is no more

[crackfoo]

BTCD market is back open on Polo, still down on Bittrex

[1714801514]

1714801514

[1714801514]

1714801514

[1714801514]

1714801514

[1714801514]

1714801514

[Shurugwi]

Just my review on Bitcoindark. I hope it could help someone =)
BTCDARK – http://www.cryptobang.com/2014/09/24/btcdark-the-cake-is-not-a-lie/

A lot of good points in your review, one thing I had a problem with is you say the price is "unstable". Yes, the price rises and falls a little as with every coin, but the rise is a constant growth. Instead of looking at the day or even week long charts, take a look at the over all growth of the coin as exhibited by this cryptsy chart

Hi! I mean that price can be overrated. BTCDARK is the most powerful among any of anonymous coins for today. But it is hard to predict the future of all the anonymous coins as well.

In all fairness... What you just said does not match what you said in your article:

"Unstable. The value of BTCD is extremely unstable – more like a rollercoaster than a reliable asset to put your money. Any better way to keep away more serious investors?"

Also 'Unstable', in the article, is a link that points to a drk/btc pair on bter. Are you sure you had all the facts or you were even looking at BTCD when you came to this ridiculous conclusion?

We all saw the competition of DarkCoin and BitcoinDark. DC was pawned, and then it was resurrect again. So, are you sure that current price for BTCD is stable? Are you sure that no more anonymous coins ll be set up soon? Some of em could provide better implements that BTCD can.

As a journalist your ramblings make absolutely no sense at all and could be likened to those a troll would spew forth.

You call BTCD price 'Unstable. The value of BTCD is extremely unstable' now you cry about DRK price and somehow try to justify your evaluation of BTCD against DRK's performance.

"Are you sure that no more anonymous coins ll be set up soon? Some of em could provide better implements that BTCD can."

WTF man! IF games? What IF the sky falls on our heads? What IF bitcoin drops below $200? What IF my dog farts? WTF has that got to do with how stable BTCD is and has been?

You need to make assessments based on the facts. Look at the graphs of BTCD since release. If you cannot see that BTCD price has been anything but unstable then you are just a troll.

Actually... It is clear now that you are just a troll. Any articles you have written have lost all credibility IMHO.

[pvnamk19]

BTCD market is back open on Polo, still down on Bittrex

May be due to this problem: http://www.reddit.com/r/Bitcoin/comments/2heu88/if_you_are_storing_bitcoins_on_a_linuxmac_system/

Jl777 uses Ubuntu to stake BTCD 

[BTCDDev]

hehe maybe those ten testers with the VPNs ran into the higgs particle while testing and fried all the circuits. ?  

Are they doing this proof of concept test within the live environment?  
That's what test networks are good for!

SuperNET integration will not cause a hard fork. Current nodes will completely ignore our testing 

[ASICHEAD]

BTCD market is open on Bittrex now

[stdset]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

[jjiimm_64]

I do own some BTCD, Am I then one of the stakeholders?     I am still fuzzy on the details.

Jim

As long as you keep the wallet open and unlock to stake then you are one of the stakeholders. The point is to keep the network as secure as possible and only people staking can make that happen. Along with gaining more BTCD, the dividend is pretty much an incentive since so much of SuperNET will be riding on BTCD. There is also mention of checking how long each user stakes to determine fairness of dividend so that opening the wallet once a month for a few hours doesn't gain the same benefit as someone that always keeps theirs' open. Basically, you are rewarded twice over for keeping the wallet open and staking.

NICE... However it says the dividends will be paid to an associated nxt addy? how does that work.

[Cassius]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

You can broadly think of it that way, though with various extra safeguards. If you use an address that has never been used before, and there is no way of tracking you outside the blockchain (which is incredibly easy in many cases) then the transaction cannot be traced to you.

Think of it like playing pass the parcel in the dark, except you and the recipient are wearing infrared goggles.

[jl777]

I do own some BTCD, Am I then one of the stakeholders?     I am still fuzzy on the details.

Jim

As long as you keep the wallet open and unlock to stake then you are one of the stakeholders. The point is to keep the network as secure as possible and only people staking can make that happen. Along with gaining more BTCD, the dividend is pretty much an incentive since so much of SuperNET will be riding on BTCD. There is also mention of checking how long each user stakes to determine fairness of dividend so that opening the wallet once a month for a few hours doesn't gain the same benefit as someone that always keeps theirs' open. Basically, you are rewarded twice over for keeping the wallet open and staking.

NICE... However it says the dividends will be paid to an associated nxt addy? how does that work.

you pick a public BTCD address to use. It doesnt have to have much BTCD in it. The software will automatically map this address to a NXT address (using its privkey), then it will make a NXT alias so that you can use the same public BTCD address even inside NXT

James

[jl777]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

There is the encapsulation of funds into a self-contained package (telepod)
This is then sent and verified (cloned) so that the anon set is all the clonings during the specified timewindow (clonesmear)

However, different users have different clonesmear parameters so the attacker wont even know what the complete anon set is.

With the addition of even a small percentage of trusted teleports, the sender's anon set is the entire duration from the sender's cloning (when the funds were received) to when the destination account clones. this could literally be everybody as it is possible to age a telepod for months.

There are random delays wherever possible to make correlations difficult. Even the selection process of what telepods to use to fulfull a tx using a genetic algorithm that is based on evolution toward the best metric, but it is a stochastic process.

Each packet is put into L onion layers. The number of onion layers is randomized so it could be 1 layer or L.

The private nodes use probabilistic routing, or rather the network uses probabilistic routing to reach the private nodes. There is no (IP <-> acct) mapping, just a statistical histogram that each node that ever received a message from the private node maintains. For nodes that never received a direct message, there is no historical data to even look at. Each private node can determine what public nodes it announces itself to, and it will use its own loopback privacy server as a gateway to do this. It is possible that a determined attacker can do some brute force sybil attack to get a higher than noise level correlation of (IP <-> acct) so if you are really privacy minded, I would advise to NEVER publish your really private acct #. Only send this really private acct number to people you absolutely trust over the encrypted network. If the attacker doesnt know your acct #, then he cant run any sybil attacks to correlate it. Also, the longer the clonesmear window, the more private, so be patient and let time be your friend

Then there is the M of N fragmenting of each telepod with probabilistic dropout at each hop. What that means is that looking at packet traffic, it is quite difficult to know if a packet coming in was meant for that node, or whether it was dropped. Nor whether a packet coming out was originated from that node or just forwarded. When M packets arrive, the telepod is reassembled just like it was sent "directly"

As you can see Teleport is a bit more than "safely sending privkeys to transaction recipient"

James

P.S. ./BitcoinDarkd SuperNET '{"requestType":"sendmessage","dest":"13434315136155299987","msg":"hello"}'

The above is how to invoke the SuperNET API sendmessage command to send the message "hello" to dest acct 13434315136155299987

[jl777]

hehe maybe those ten testers with the VPNs ran into the higgs particle while testing and fried all the circuits. ?  

Are they doing this proof of concept test within the live environment?  
That's what test networks are good for!

SuperNET integration will not cause a hard fork. Current nodes will completely ignore our testing 

However the multisig expansion and PoS v2 will cause a hardfork

[stdset]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

There is the encapsulation of funds into a self-contained package (telepod)
This is then sent and verified (cloned) so that the anon set is all the clonings during the specified timewindow (clonesmear)

However, different users have different clonesmear parameters so the attacker wont even know what the complete anon set is.

With the addition of even a small percentage of trusted teleports, the sender's anon set is the entire duration from the sender's cloning (when the funds were received) to when the destination account clones. this could literally be everybody as it is possible to age a telepod for months.

There are random delays wherever possible to make correlations difficult. Even the selection process of what telepods to use to fulfull a tx using a genetic algorithm that is based on evolution toward the best metric, but it is a stochastic process.

Each packet is put into L onion layers. The number of onion layers is randomized so it could be 1 layer or L.

The private nodes use probabilistic routing, or rather the network uses probabilistic routing to reach the private nodes. There is no (IP <-> acct) mapping, just a statistical histogram that each node that ever received a message from the private node maintains. For nodes that never received a direct message, there is no historical data to even look at. Each private node can determine what public nodes it announces itself to, and it will use its own loopback privacy server as a gateway to do this. It is possible that a determined attacker can do some brute force sybil attack to get a higher than noise level correlation of (IP <-> acct) so if you are really privacy minded, I would advise to NEVER publish your really private acct #. Only send this really private acct number to people you absolutely trust over the encrypted network. If the attacker doesnt know your acct #, then he cant run any sybil attacks to correlate it. Also, the longer the clonesmear window, the more private, so be patient and let time be your friend

Then there is the M of N fragmenting of each telepod with probabilistic dropout at each hop. What that means is that looking at packet traffic, it is quite difficult to know if a packet coming in was meant for that node, or whether it was dropped. Nor whether a packet coming out was originated from that node or just forwarded. When M packets arrive, the telepod is reassembled just like it was sent "directly"

As you can see Teleport is a bit more than "safely sending privkeys to transaction recipient"

James

P.S. ./BitcoinDarkd SuperNET '{"requestType":"sendmessage","dest":"13434315136155299987","msg":"hello"}'

The above is how to invoke the SuperNET API sendmessage command to send the message "hello" to dest acct 13434315136155299987

I don't see how doublespends coud be prevented with this approach.

[jl777]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

There is the encapsulation of funds into a self-contained package (telepod)
This is then sent and verified (cloned) so that the anon set is all the clonings during the specified timewindow (clonesmear)

However, different users have different clonesmear parameters so the attacker wont even know what the complete anon set is.

With the addition of even a small percentage of trusted teleports, the sender's anon set is the entire duration from the sender's cloning (when the funds were received) to when the destination account clones. this could literally be everybody as it is possible to age a telepod for months.

There are random delays wherever possible to make correlations difficult. Even the selection process of what telepods to use to fulfull a tx using a genetic algorithm that is based on evolution toward the best metric, but it is a stochastic process.

Each packet is put into L onion layers. The number of onion layers is randomized so it could be 1 layer or L.

The private nodes use probabilistic routing, or rather the network uses probabilistic routing to reach the private nodes. There is no (IP <-> acct) mapping, just a statistical histogram that each node that ever received a message from the private node maintains. For nodes that never received a direct message, there is no historical data to even look at. Each private node can determine what public nodes it announces itself to, and it will use its own loopback privacy server as a gateway to do this. It is possible that a determined attacker can do some brute force sybil attack to get a higher than noise level correlation of (IP <-> acct) so if you are really privacy minded, I would advise to NEVER publish your really private acct #. Only send this really private acct number to people you absolutely trust over the encrypted network. If the attacker doesnt know your acct #, then he cant run any sybil attacks to correlate it. Also, the longer the clonesmear window, the more private, so be patient and let time be your friend

Then there is the M of N fragmenting of each telepod with probabilistic dropout at each hop. What that means is that looking at packet traffic, it is quite difficult to know if a packet coming in was meant for that node, or whether it was dropped. Nor whether a packet coming out was originated from that node or just forwarded. When M packets arrive, the telepod is reassembled just like it was sent "directly"

As you can see Teleport is a bit more than "safely sending privkeys to transaction recipient"

James

P.S. ./BitcoinDarkd SuperNET '{"requestType":"sendmessage","dest":"13434315136155299987","msg":"hello"}'

The above is how to invoke the SuperNET API sendmessage command to send the message "hello" to dest acct 13434315136155299987

I don't see how doublespends coud be prevented with this approach.

the blockchain is used to verify the funds before crediting the sender

[clovis A.]

I tryed reading the whitepaper, although I didn't read it to the end. Do I understand right, that basically the idea is safely sending privkeys to transaction recipient?

You can broadly think of it that way, though with various extra safeguards. If you use an address that has never been used before, and there is no way of tracking you outside the blockchain (which is incredibly easy in many cases) then the transaction cannot be traced to you.

Think of it like playing pass the parcel in the dark, except you and the recipient are wearing infrared goggles.

I love this analogy Cassius!!  It's original and it made me smile seeing the mental picture

[jl777]

I am doing a design level review with anonymint via PM
Also Kristov Atlas will be doing a review, hopefully of both the design level and the code conformance to the design

James

[jl777]

just had first successful SuperNET message from one of my servers to someone else's server!

[BTCDDev]

just had first successful SuperNET message from one of my servers to someone else's server!

I hope everyone here appreciates what is going on right now!

SuperNET is now being actively tested, anyone who knows their way around a command line can volunteer to help out over at forum.thesupernet.org

I am very excited about where we are headed value-wise. This is going to change our community for the better

Matthew

[tjmaruy]

sweet, all u do is greatly appreciated very much

[benthach]

the darkhole is dying

[stdset]

the blockchain is used to verify the funds before crediting the sender

Alice wants to buy something from Bob and Jack, but has enough money only for one purchase, not both. Nonetheless she sends her privkeys to them both, they verify that funds indeed belong to the privkey, and send her the purchases. After waiting reasonable amount of time, so that the purchases already sent, Alice performs regular onchain transaction sending the funds to herself.