BTCD is no more

[SHossain]

There is no reason to sell atm

I bought few more at 0.0123 Love the cheap coins.

[Counterpartybtc]

the price is cheap. buy some.
I will sell at 0.2btc.

[jl777]

I'm far from an expert on this stuff, but it's my understanding that there's a couple problems with PoS. The first being that those that hold the majority of the coins basically control the network. i.e. Like a 51% issue.  The other problem is that when people are staking, there's no economy going on. Sort of a catch 22 thing. You need people actually using the coins for it to gain wide spread acceptance and use, and yet you need people staking to secure the network. I recently read about some coin that was changing it in some way so that actually using the coin would increase your stake in some way.  There was also a paper out in June about Proof of Activity that I think tried to address these issues but it's a bit above my head at this point.  So basically I'm asking if BTCD has done anything like that or if it's the "typical" PoS.

These aren't problems. The majority of coin holders controlling the network is the ideal situation, since these are the ones who are most incentivised to maintain the coin's value and worth. It means a 51% attack is extremely difficult since an attacker has to buy a majority of coins, and as he starts buying the price goes out, making it many times more expensive than a PoW attack.

There is no conflict between staking and spending. Not all coins need to be staked for the network to be secure, and there will never need to be a situation where a huge percentage of coins are actively being traded at a single instance in time. When the coins aren't actively moving they can be staked.

Basically PoS has many advantages over PoW, so those who prefer PoW coins will often have to make up reasons why their system is better.

I understand that PoS has advantages over PoW.  But it also has some disadvantages.  I just finished reading through both the BC PoS V2 and Reddcoin PoSV white papers. They both outline the various problems/issues with PoS and they both have implemented things to try and deal with some of those issues. I also ran across this paper http://www.cs.technion.ac.il/~idddo/CoA.pdf which discusses a Chain of Activity protocol to resolve some PoS flaws and it was spun off from PoA that I found here https://bitcointalk.org/index.php?topic=659275.0.

As I said in my post, I'm asking if BTCD has done anything along those lines.  I would have to assume it hasn't given the responses.

The dev repo has BC PoS v2 implemented

[lordnitro]

Hey guys, I still do have a problem with block 100675 :-(
Got youre user.conf, starting as admin, deleted wallet expect of wallet.dat, its not getting trough that block :-(
Any ideas? Any help? I need to work with that wallet, got that problem for some days now :-(

make sure to backup the wallet.dat!
it is all the other files that need to be cleared out (other than the .conf)
then restart and it shouldnt get stuck

already did that, days ago :-)
still not working, i do have 8 connections to the network...

[jl777]

Hey guys, I still do have a problem with block 100675 :-(
Got youre user.conf, starting as admin, deleted wallet expect of wallet.dat, its not getting trough that block :-(
Any ideas? Any help? I need to work with that wallet, got that problem for some days now :-(

make sure to backup the wallet.dat!
it is all the other files that need to be cleared out (other than the .conf)
then restart and it shouldnt get stuck

already did that, days ago :-)
still not working, i do have 8 connections to the network...

i assume you are using the latest version
you could try the experimental version if you are brave

[visual111]

coinomat is playing a role in teleport, right?

[jl777]

coinomat is playing a role in teleport, right?

via cryptocard, yes

[jl777]

The initial code reviews are coming in: https://nxtforum.org/index.php?topic=4940.msg104968#msg104968

No critical bugs found, but still need more people to analyze the code.

Made some progress with the probabilistic routing. had to pass through two new data items through all the API calls, up and down the whole scale. So a lot of changes in the files, but really just a few things.

then the confusion over the peer<->peer connections vs ip<->ip connection, sent me down the wrong path a bit, but it is becoming clearer how to differentiate the logical app level "connection" vs the low level ip<->ip connection

I also decided to pass through the ip/port info from the p2p network into my code. I need to make sure that even using this info that nothing critical is leaked as an attacker could make this change to extract info. Better if I am seeing the data and making sure it is scrubbed!

I need to think through things a bit more to make sure the routing will converge. I think I might have a pretty good fallback, but am worried about leaking the IP info to a compromised privacy server. A solution to the privacy server not even knowing the IP will be a big breakthrough. My fallback is to only have the loopback privacy server know your IP and then make sure your privacy cant be deduced.

Since I am waiting on some changes from BTCDdev, I will have time to push forward on this part. I am not worried about the routing between all the public privacyServers, so even with the probabilistic routing still being improved I can switch to debugging Teleport next week.

The TOKEN sales looks like it will end in 2 days, so that whole time eater will also become much less and I can get back to 75%+ on coding soon. Thank you for you patience.

James

P.S. also today I got caught up in the whole BCX XMR thing which was quite distracting as I was in the loop of all the PMs

[Cassius]

P.S. also today I got caught up in the whole BCX XMR thing which was quite distracting as I was in the loop of all the PMs

What happened with Monero? It just tanked.

Edit: found it. https://bitcointalk.org/index.php?topic=789978.0

BBR affected too?

[jl777]

P.S. also today I got caught up in the whole BCX XMR thing which was quite distracting as I was in the loop of all the PMs

What happened with Monero? It just tanked.

Edit: found it. https://bitcointalk.org/index.php?topic=789978.0

BBR affected too?

If you can decipher: https://bitcointalk.org/index.php?topic=789978.msg8909623#msg8909623
plz let me know.
at this point anybody that says they know, is wrong

my sense is that many things have to be done at once and CZ already fixed a key part of this whole attack vector, but anonymint's math stuff makes my head hurt, so I think it is unlikely even for XMR and even more unlikely for BBR, but it all depends on the undecipherable (to me) math

[jl777]

OK, got the new code debugged.

Now all three servers know each other's public privacyServer info and this is with minimal packet traffic, actually I think it is using the theoretical minimum. I am ignoring the IP leak for now, it will be much easier to scrub that when the system is more fully in place.

What is working now is that any public privacyServer will be able to contact any other and each such public privacyServer is actually a loopback server for a private node.

I will try to get the public to private comms working tomorrow and if all goes well, private to private. Once any private node can talk to any other, then I need to scrub or randomize the IP info leakage. have some ideas already, when I see all the private to private comm sequence I can verify if these ideas will work.

the hard part for tomorrow is to make an algo that allows private to private node comms without explicitly knowing any actual coinaddr<->ipaddr pairs

James

[jl777]

OK, got the new code debugged.

Now all three servers know each other's public privacyServer info and this is with minimal packet traffic, actually I think it is using the theoretical minimum. I am ignoring the IP leak for now, it will be much easier to scrub that when the system is more fully in place.

What is working now is that any public privacyServer will be able to contact any other and each such public privacyServer is actually a loopback server for a private node.

I will try to get the public to private comms working tomorrow and if all goes well, private to private. Once any private node can talk to any other, then I need to scrub or randomize the IP info leakage. have some ideas already, when I see all the private to private comm sequence I can verify if these ideas will work.

the hard part for tomorrow is to make an algo that allows private to private node comms without explicitly knowing any actual coinaddr<->ipaddr pairs

James

good job 

+1! good to see you coding alot again

only half a day and that was full of distractions. code just worked pretty much the first time, only a few silly typo level errors so it just looked like I spent a lot of time

[Qwitnix]

A few more questions about the wallet.

Is there a way to see if all lines of the BitcoinDark.conf are read without errors?
Is it ok to add a section head in the .conf like used in an ini file? [Settings] or something?
In the examples the .conf files all start with the rpcuser= and end with a list of the addnode=. Is it ok to mix up the sequence of the lines in the .conf? so start with a addnode= then the rpcuser= then another startnode= etc.

Is there a unique version number for each new version of the wallet?
if so, where can I find it?
if not, are you planning on doing that? It would be user friendly to have it, and I would like to try and use the same version numbers in the installer.

That's it for now.
Grtz,
Qwitnix

[TeseracT]

is problem with withdrawing from cryptsy resolved? Or should I be prepared that my BTCD will stuck?

[alxx77]

I'm trying to run a wallet on windows, but nothing is happening... where should bitcoindark.conf be located: in same folder as exe or in data folder..??

is there some specific network settings that should be done..?

 

[Qwitnix]

I'm trying to run a wallet on windows, but nothing is happening... where should bitcoindark.conf be located: in same folder as exe or in data folder..??

is there some specific network settings that should be done..?

As far as I know, you should place the bitcoindark.conf in the C:\Users\<YourUserName>\AppData\Roaming\BitcoinDark folder.

PS. I'm still working on the installer. Just need a bit more info and time.

[alxx77]

It's working now, but it appears that it needed some time to start syncing...

[apex944]

OK, got the new code debugged.

Now all three servers know each other's public privacyServer info and this is with minimal packet traffic, actually I think it is using the theoretical minimum. I am ignoring the IP leak for now, it will be much easier to scrub that when the system is more fully in place.

What is working now is that any public privacyServer will be able to contact any other and each such public privacyServer is actually a loopback server for a private node.

I will try to get the public to private comms working tomorrow and if all goes well, private to private. Once any private node can talk to any other, then I need to scrub or randomize the IP info leakage. have some ideas already, when I see all the private to private comm sequence I can verify if these ideas will work.

the hard part for tomorrow is to make an algo that allows private to private node comms without explicitly knowing any actual coinaddr<->ipaddr pairs

James

good job 

+1! good to see you coding alot again

only half a day and that was full of distractions. code just worked pretty much the first time, only a few silly typo level errors so it just looked like I spent a lot of time

Good news.  Do you need any additional help with testing remote nodes etc?

[id10tothe9]

P.S. If anybody is on a Mac, can you try to build following the instructions on https://github.com/jl777/btcd
It is still a dev version and can be any state of bugginess, but the build process can be verified and this will help save time. So, the question is if it builds and links. you can run it too, but please dont keep it live as I am trying to keep a controlled test going

I'll try that, but might take me till the weekend since I'm short on time

I'm trying to build it now, but the first link in the readme-qt is not working: http://qt.nokia.com/downloads/sdk-mac-os-cpp
I'm guessing should be the same if I download this? http://qt-project.org/downloads

[mamamae]

for anyone with wallet problem
copy your wallet file
cancel everything from the bitcoindark folder
C:\Users\<YourUserName>\AppData\Roaming\BitcoinDark
redownload wallet and file conf in the first ann page
copy file conf and wallet file in bitcoindark
then start bitcoindark qt.exe

when is stuck at 64xxx or more block or something quit the program and restart it