Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 65. (Read 284526 times)

Couple of brackets to solve issues hopefully https://github.com/bitcreditscc/bicreditsnew/pull/52

Also tested getwork miner , looking good.  AFAIK getblocktemplate miners are invalid as they would not know what to do with grants and bids. The occasional crashes caused by exception in bid tracker side stepped by using "try/catch".

Going to try and get external miner source code and see how i can improve internal miner.

Looked at the superblock, yeah, i noticed. I am looking into it, it's not miner issues, it's me, i messed up again somewhere. If the internal iner had been correct, the output count would have been higher, but somewhere there is a missing link.

also bittrex hasnt been open for bcr deposits or withdraws for 2 weeks. anyone who wanted to sell or buy has likely done so especially with a 50% price spread.

Also bid superblock failed again

Anyone else noticed how since mining had new rules..... no real trades made? Because miners were the ones selling off  even at a loss to cover cost. Now that you actually have to be invested.... no-one is selling.  

I will try to build an win enviroment against this versions.
For now, on windows, i build against:

Boost 1.57.0
Curl 7.44.0
DB 4.8.30
Libpng 1.6.16
Miniupnpc 1.9.20150206
Openssl 1.0.1l
Protobuf 2.6.1
Qrencode 3.4.4
QTbase 5.3.2.7
QTTools 5.3.2.7
Qrencode 3.4.4

Bitcreditscc, could you post your dependencies versions also ?

Not much help.
If a close and restart the wallet, and was on the same block, he starts fine.
If the local blockchain was at least one block behind, first time when i start the wallet, close. At second start it goes fine.

It's been kinda hard for me to keep up with the wallet versions and things. I tried the addnodes but no connections still. Is the config still suppossed to look like this?

rpcuser=UNIQUE_USER_NAME
rpcpassword=UNIQUE_PASSWORD
rpcallowip=127.0.0.1
rpcport=xxxx
allowip=xxx.xxx.x.xxx
listen=1
daemon=1
server=1
genproclimit=0
banknode=1
banknodeprivkey=MY _BANK_NODE_KEY
banknodeaddr=127.0.0.1:xxxx
irc=0
addnode=91.230.123.101:8888
addnode=91.230.123.11:8877
addnode=82.211.1.181:8877
addnode=91.230.123.101:8877

guess it would be a lot of work to reject a superblock that doesnt have payouts via code. maybe reject if it doesnt have tx # vout whatever in excess of # of addresses shown in bidtracker. also im assuming it will work that if this next block works properly it will zero out the balances/bids and/or generate new bid deposit addresses.

Might have been a miner running a noncompliant build or mining software. networkhashps is up at 52 and diff in the hundreds again, someone's taking advantage of the only two consecutive blocks rule. Hopefully the next release will up it to 1/20 or 1/40 which will make it far less likely and more expensive to hijack a superblock.

Still possible for someone to strategically begin throwing hash at the chain just before the superblock though. There needs to be a way for any hijacked superblock to get rejected by the rest of the network, make it unspendable by the hijacker. Followed by automatic encryption of their home folder, ransom for the password payable to the BCR communal reserves.  

Done, crude, unfinished and ugly but it might help show if the problem is here or not.

@dragos - transactionview.cpp and transactionview.h  http://s000.tinyupload.com/?file_id=28914725737094427125 - can you swap these into your Win build and see if it helps with anything? Hides the history until you click the Show History button.

Couldn't get the Export button to show again (without a segdump  ) after hiding it initially but that can be looked into if this helps whatever prob Win users are having.

fair enough, meanwhile

any changes in place for the next bid cycle in 300 blocks? did you guys narrow down why that 1 address got the entire payout?

also I dont see a vote tab in the windows wallet.

Eventually, this will be put in a far more stable database with better handling of errors. Right now we are mostly doing proof of concepts, expansions, mods and some debugging. At some point, the foundation will be complete, then we'll go module by module , optimizing and sanitizing. The job is for a team and will take a while to do alone.

loaded fine, went to readd my conf and it wouldnt reload. so started fresh from bootstrap with proper conf and its all set. very very finicky.

Boost libs - I have a hellish mixture of 1.55 1nd 1.54 

Berkeley DB 4.8.30

libpng12-0:amd64          1.2.50-1ubuntu2   amd64           
libpng12-0:i386           1.2.50-1ubuntu2   i386           
libpng12-dev              1.2.50-1ubuntu2   amd64           

libminiupnpc-dev          1.6-3ubuntu2.14.0 amd64             
libminiupnpc8             1.6-3ubuntu2.14.0 amd64           

openssl                   1.0.1f-1ubuntu2.1 amd64             

libmirprotobuf-dev:amd64  0.1.8+14.04.20140 amd64             
libmirprotobuf0:amd64     0.1.8+14.04.20140 amd64             
libprotobuf-dev:amd64     2.5.0-9ubuntu1    amd64             
libprotobuf-lite8:amd64   2.5.0-9ubuntu1    amd64             
libprotobuf8:amd64        2.5.0-9ubuntu1    amd64             
protobuf-compiler         2.5.0-9ubuntu1    amd64             


libqrencode-dev           3.4.2-1           amd64             
libqrencode3:amd64        3.4.2-1           amd64             
qtbase5-dev:amd64         5.2.1+dfsg-1ubunt amd64             
qtbase5-dev-tools         5.2.1+dfsg-1ubunt amd64           
qtbase5-private-dev:amd64 5.2.1+dfsg-1ubunt amd64             

qttools5-dev              5.2.1-8build1     amd64           
qttools5-dev-tools        5.2.1-8build1     amd64           

curl                      7.35.0-1ubuntu2.5 amd64             
libcurl3:amd64            7.35.0-1ubuntu2.5 amd64             
libcurl3-gnutls:amd64     7.35.0-1ubuntu2.5 amd64           
libcurl4-openssl-dev:amd6 7.35.0-1ubuntu2.5 amd64             
python-pycurl             7.19.3-0ubuntu3   amd64           
python3-pycurl            7.19.3-0ubuntu3   amd64             

it's because grantdb.dat is out of sync with the blockchain. at present time, it can not be reconstructed.
here it is the blockchain at 210023 https://mega.nz/#!Lxsj3LRI!jwam12_Vbg4NS-alkZySe4JvhxUOwUM2q2nNgwRoHgw
delete everything except backup, bitcredit.conf, miningkeys.dat and wallet.dat, unzip-it and sync from there.

windows latest build, i have im running a blank config now and it runs, but its stuck at 211089
*deleted peers.dat to try and find new ones. shows me now 5 peers, one lists blockheight 210242 the rest are synced. the one fucked up one is version 17.3, not sure if he's holding me back.
seems to think its fully synced, ill let it wait a bit and see if it decides otherwise and starts processing blocks.

did you by any chance shut down and restart? is this windows or linux?

Voting Overview

There are [5] initial prefixes that are used for voting all of which allude to a purpose, dof, tof, sof, mof, are jobs, namely development, technical, support and marketing. bnk is for banknode voting and the last is for custom prefixes. The recognized prefixes start with 6BCRxxx so for example, my job as dev is voted for on 6BCRdofxxxx. Votes are counted every 5 blocks and a small stipend is paid to the occupier of the office. If one under performs, users can replace him/her/them by voting elsewhere.

A vote is 1000 sats(we'll need a new name)

Votes are based on overall weight , so even if you spam vote, if a total number of coins outweighing you votes elsewhere you lose. This is because simply, one man one vote cannot work in an anon system like ours, since basically anyone can make a new address and vote from it, what matters is both the vote count and the overall monetary backing of this decision. This also prevents scammers messing with the system as investors can correct the ship as they see fit.

the bnk prefix is meant to be used to vote for banknodes based on their service, so if you like a particular bank, you can vote for it. When the ratings are included the top ten banks will be listed in the wallet and are the recommended services to users.

Votes are final, developer will never get involved unless there is imminent danger to the system stability, note i only care about the system, who you vote for to run everything else is none of my business. BN votes will carry additional weight calculated based on trust ratings and ranknings.

So choose a prefix and get an address , let's get started.

are we forked again? chainz reports same hash as i have for 211089, but theyre on 211131. my client reports 211090 Invalid:

*edit side note
this is very wonky. walletc rashes on reload with my bitcredit.conf  if i move it out of the datadir wallet loads fine, i move it back in it doesnt work. it was just running with no changes.. i even tried commenting everything out. still doesnt work.

i think i have a fix  

blacklisting involves a lot of work, but it can be done. We can ensure that users can't game the system by adding moderation and mandatory wait periods. Also remember we have a trust engine that will prevent typical scammers from getting finances.

Votes by BNs are the only ones that can blacklist an address, being on the watchlist takes 1 vote , all out ban takes 50 votes. All votes must be  from active BNs with trust ratings  above a certain mark.

Man, if i just had clones of myself, we'd be that much farther in.