Perhaps I've grown accustomed to trading in larger numbers, but don't these tiny numbers (in BTC and BTCD) seem a little artificial?
I'm absolutely not trying to talk things down, because we all know where this coin is heading (and it ain't down) 

150 BTC per day is close to NXT trading volumes, so not sure what you mean...

It might seem artificial to you, but thats all there is of BTCD and at 5% per year on <1.2 million coins its not like it grows on trees.
The other promising coins like XMR are being mined like crazy and that creates daily tens of thousands of coins that need to be sold to pay the mining fees.

Take away the selling pressure and any small continual demand will create a stable floor. Any news stories like salsa is getting keeps pushing things up. I am disappointed people are not donating more to him. Please fund salsa to get more PR, unless you dont like the higher prices and liquidity.

James

I'm not talking about the total volume, I'm talking about the single trades. It's mostly single or low double digits BTCD per trade. On average very small trades.
Perhaps it's normal and I'm seeing things that aren't there...

Wow, what was up with that?!  
Someone either made a mistaken, wanted to get rid of coins NOW or trying to push things down a bit (which didn't work).

Unfortunately I had my buys around 83000... Could have gone lower. Oh well, at least I didn't loose anything.

my first bid was @80k when I saw that dump only to 81K and i figured i should lower it and I got lucky.

got all my coins back plus i have extra btc now laying around

Oh, you are talking about the ask side. Well of course, only WH is selling below .001
And with so few coins, I am surprised to see the occasional 1000 BTCD lot for sale, very tempting for me, but I have enough now and I think better for more people to get a taste

James

P.S. I have yet to sell a single BTCD and dont expect to until we go above DOGE marketcap
Then I will sell some, maybe enough to buy a real Shiba doggie

For reference, I found a discussion between myself and AnonyMint. For those that know him, I dont need to tell you about AnonyMint. For those that dont, he is brutally honest, very smart and obsessive about anonymity. He worries about stuff like future Quantum Computers cracking all current day encryptions!

So, this thread gives some insight into where I was several months ago:
https://bt.irlbtc.com/view/470987.msg5581647#msg5581647

Now many of the design details have changed, some thanks to AnonyMint's feedback. As he says the key is being able to trust your privacyServer. Everything revolves around this, so for the truly paranoid, the solution is to setup your own privacyServer. If you cant trust yourself, then who can you trust?

I suggest that people that want to setup privacyServers for the public to use to start preparing now. People will want to know you, to be able to trust you as their privacyServer provider. I will make it so that privacyServer nodes get a percentage of the business that flows through them, eg. InstantDEX commissions. You will also earn nodecoins just for running a node. The privacyServers will eventually need Ddos protection, decent bandwidth, enough RAM. Not sure of the exact specs, but considering the hardware BTCD community put together to get 3 petahashes(!!), I dont see a big problem in getting enough privacyServers setup.

So, it will be a hub and spoke topology and we need to get more hubs than DRK has masternodes. However, just having nodes is not enough, we need to have each hub have at least 10 active users, otherwise attackers can use timing and knapsack analysis to deanonynimize.

I am envisioning the privacyServer providing many services, for example I already have a squid http/https proxy automatic install script. This allows you to get subscribers for http proxy service, which runs about $5 per month. Probably best to charge less to get more customers.

James

Hi everyone,

For those of you who have been in the irc, I need no introduction. For the rest of you, I am BTCDDev, one of the core devs on this project along with jl777, Azeh, and Torrn. I will be posting here along with them updates, some technical and some not, as we go along. Just though I would introduce myself.

 

Just finished coding a basic onion routing support, the confusing part is that you can make requests locally, to the privacyServer or even via broadcast. I want to minimize redundant code so I funnel everything to a single process_packet function, so client, or server or broadcast or tcp or udp, all get processed in the same place.

Somehow it seems to be way too little code for what it does.

Anyway, time for some lunch and then debugging

Once the encrypted comms are stable in the new setup (I had a hardcoded client/server test working), then all but the initial handshake will be encrypted with a session specific public/private key using Daniel Bernsteins nacl library: http://nacl.cr.yp.to/index.html

I use the NXT token generation to sign every packet and it is even timestamped so even if somehow it gets intercepted and decoded, it can't be used in a replay attack.

Its really not anything very spectacular to just send messages back and forth, but this is the foundation on which all the rest of the code will use. Being able to say "send this message to that account" and having it magically get there and being totally encrypted is a very useful foundation.

Sorry it is taking so long, but this is critical code and any loose end could allow attacker to deanonymize, so I have to go slow and careful.

James