Do you have blackcoin client on while trying to start Blackhalo?
No should i have it opened or not?
No still have no changes and when my antivirus is disabled- ESET .System is win7 32bit, and i don't have troubles with wallet at all, syncing well and this happening very rarely. I had few problem with cgminer but this is not related with this i assume.
It shouldn't be running. I got this same exact error. I closed my Blackcoin QT and blackcoind started working.
Yeah the issue is not with Halo, its with Blackcoind. It might have already been running or Blackcoin-QT or like it says antivirus(check task manager). We used to have a problem with avast blocking python but we sent our program to them and i think its no longer an issue. You can always build from source of course at
www.davtonia.com/bithalo/haloobf.zipAs for finishing NightTrader this has been discussed before. First off, I have a few more templates to finish (python contracts, barter, buy/sell) those make the client more user friendly. The question of NT is weather or not I will make it a microtrader or not. Let me explain the problem I ran into, it didn't have anything to do with coding per se.
If we do it the way I had intended, we can do NightTrader by the following methods:
MICROTRADING:
THE ORIGINAL plan was to microtrade under double deposit (this can already be done actually if you do it manually under a contract). Where the software would automate payments (BTC for ETH or LTC for DOGE etc) and the deposits would be double deposit in Blackcoin. So lets say you want to trade 1 BTC for 90 ETH you would deposit .5 btc each of BLK and trade like this:
.25 .25 .25 .25 until the trade is complete
That seems great but the problem I foresee is this... will anyone use a decentralized exchange that has to wait for Bitcoin confirmations?! This means the trade can take up to an hour unless you use online services to confirm early. Also many deals might be for higher amounts AND you would need to do that contract with all traders on the order book.
So Bob wants to trade with Alice, Joe and Steve because they ALL had orders on BlackHalo. So they arrange deposits in BLK and can end up doing anywhere from 4 to 50 transactions for the same trade. (imagine 500 btc wall waiting for hundreds of little payments)
All this live trading bloats the blockchain. So it works but WILL PEOPLE USE IT???
Will people buy Blackcoin just for the deposit? And will rising in prices of Blackcoin and then dumping in some cases make the deposit value go below the trade causing defaults? We would need higher deposits then.
I had a huge problem with BlackHalo and BitHalo. I thought BitHalo would replace localbitcoins because you don't need to trust anyone, not even an arbiter. But if nobody uses BitHalo what the hell was the point? Nobody sells anything on the markets, it was years ahead of Ethereum and Open Bazaar, translates to 92 languages has like 50 different little features (joint accounts, steganography etc) and still never got used by the masses.
So imagine if I build an exchange interface for NightTrader to do microtrading and then nobody even uses it because its not lightning fast like poloniex and they have to form multiple contacts. Also being peer to peer if any of your trade partners disconnect during a trade that would greatly extend the amount of time you are waiting for the trade to finish. Its amazing that we can do decentralized exchange this way but I want people to use what I make and not deal with the same bullshit of not having users.
Granted I don't advertise, but its hard to advertise and code.
Plus should I list all the orders on my decentralized markets? Because then it means waiting for the POW on each order which can make for a slow orderbook where orders are accepted out of order. Its a tricky engineering job. I can do it but i would want users and some sort of knowledge that my 1000s of hours of coding wasnt in vain.
So here is the OTHER options:
ATOMIC TRADING:
This is a great idea, we use checklocktimeverify to do trades between coins. The problem here is, this doesn't make NightTrader Blackcoin centric and it just means Blackcoin is listed as a coin. Also this means only coins with checklocktimeverify can get on the exchange (Blackcoin, Bitcoin, BitBay, Ethereum etc)... there is very few coins with true locktimes. And adding Ethereum is a custom contract meaning more work if I want to add them. Also it still means multiple trading partners and more than one transaction per trade. Granted its dropped to only a couple transactions per trade which is wonderful but still speed is the issue.
MULTISIGNATURE EXCHANGE:
So this is one of my original ideas but again its not BLK exclusive. Basically the exchange holds the 2nd key to all joint accounts. Then users sign over transactions of SIGHASH SINGLE for their change which is blank checks basically where the exchange routes IOUs to the users. There is a couple problems, the same as BitSquare, there is still a security risk that the exchange can collude. And even without exchange collusion a hacker who gets exchange signing keys can effectively try double spending by getting involved in trades and defaulting. Its not as secure as it looks. Sure its 100 times more secure than a normal exchange but is it truly worth the effort?? And plus I have to take the liability of holding that exchange key. So I'm subject to the laws of governments who will say I'm holding the key and this added responsibility is very unattractive.
The advantage? Its fast.
LIGHTNING NETWORKS:
Again this is much like multisignature exchanges, this creates a "Mt. Box" for routing live daisy chained micropayments. The problem here is the same (and by the way Lightning networks look very insecure to me because of this). The exchange can simply collude with itself and withdraw pretending to be a trade partner. The only way to avert this threat is if the exchange had collateral in frozen coins which requires pegging so this is like ultra future tech. Also it requires crazy segwit, servers and tons of engineering.
I'm not entirely sure why everyone loves lightning networks so much. True its really brilliant engineering. But it gives too much power to the exchange. Since the exchange doesn't actually put up collateral you have access to, the only way to make "Segwit" work is with a pegging frozen coins system where Mt.Box is sitting on tons of frozen collateral so they have to be very wealthy to begin with and then use that as a deposit in case they collude.
Otherwise the only way to do P2P payment routing is by forming joint accounts with many people and using the lightning network principals with withdraw from those daisy chained payments and form multiple relationships and then it would never be "off the chain" it would only be less bloat and a little bit more P2P. That's the only trustless way. Of course you can always prune the blockchain and not care about bloat (bandwidth might be the bigger problem anyways which is why P2P options are more attractive). Then again there is always servers than can host all that data too. Is bloat the biggest problem or not? How many terabytes does facebook process a day? 500?
Lightning networks should not be a "Mt. Box All the users" relationship it should be a daisy chained "all the wealthy users routing payments to everyone else" kind of network. That is still P2P bloat free and it means settlement will happen all the time to form new relationships for missing joint partners. That I think would completely prevent collusion since in the case of the "rich users" example, they would put collateral. Of course Mt. Box can put collateral and should. Can we assume they will be holding any funds to begin with?
So you guys can give me your thoughts but I'm stuck. Thats why I'm just building out BlackHalo and waiting to see if it catches on before going and committing myself to another couple years of coding for no clear purpose(when it comes to NightTrader).
BlackHalo on the other hand is improved so much in the last year people should really try it. It will be 100% done for commercial use this year. Its already pretty commercial, but there are more templates and an api to finish.
