Are you able to package the linux qt binary with the stylesheet.qss and vanilla.qss files? Without them the client is missing the bottom toolbar if they haven't compiled it themselves...     Maybe we can make a little self-extracting zip/tar script to create a basic bitcredit.conf  etc.?

Does the Win version have a desktop icon?

Easy fix which I never quite get around to. Will do it tomorrow.  

edit: I have unchunkified the sync progress bar, ! never normally see it but was testing everything worked on a clean *buntu 14.10 box. (It did.)

The wiki needs updating I think though as I got an error on execution:
"/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./bitcredit-qt)"

- fixed with:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install libstdc++6-4.7-dev
sudo apt-get install libstdc++6

Same thought had occurred to me. People just love rank and status...  

I was thinking of having a sliding scale of BN bid reward based on collateral amount too, with a bias towards 'smaller' smartnodes to encourage more instances of them.

eg 250k BN gets 16 BCR, 50k BN gets 4 BCR? Enough of a delta there to make it worth the extra effort. Maybe something to consider, I'm happy either way though.

Could make the collateral amount function like binary in terms of your available options:
|     |     |     |     |     |     |     |     |
256 128 64  32   16  8     4    2     1K

ie. if you have 128k collateral you could be 1 128k node, or 2 64k nodes, or a 64k and 2 32k nodes, or 4 32k nodes... etc.

Bet he never did manage that and it's an unsolved puzzle to him to this day...  



What's the wanting another explorer thing about? There's a perfectly good one built into the wallet.

Well banknodemanager.cpp is about as close as you can get to a mine field without actual explosives. I thought it was going to be a 30 minute walk in the park... still unsure why the current configuration works while the previous thirty seven perfectly good iterations were segfault superattractors...

Do we think it would be handy if we could see our own BNs in the QT list more easily? Right now there are 23, in a few weeks there will be >100...

Filter is by pubkey, as IP address is not necessarily accurate.

WIP - stick your pubkey(s) in a text file called mybanknodes.txt and voila... there are certainly more elegant ways of doing it but I'm not clever enough and I'm sick of the compiler moaning at me.


No those are not all mine, just a random selection for demonstration purposes.

 

Nothing idealistic about it, my life is thus made serene... since I put everyone on some flavour of linux about 16 years ago, petulant demands for free IT support have dropped by appx. 99%.   

Last time I tried running a webserver (on my BN VPS) the instance got hacked within 48hrs and was spewing gigs of UDP packetry as a node in some DDOS network... 

Which is odd because my firewall should have completely blocked all UDP traffic in or out, I suspect ufw doesn't actually work properly on OpenVZ VPS's.

Anyone who wants working linux bitcredit-qt/bitcreditd/bitcredit-cli binaries please PM me with an email address to send them to, until we get a proper website set up... 

I have submitted a pull req to disable the exchange browser if "noexchange=<anything>" line in bitcredit.conf.

Tested as working on xubuntu 14.04, I can't test this or anything else on Windows as Crouton Mansions is a MS free zone.

After every new build I need to delete mncache.dat, after doing that the wallet loads fine.

You can at block 145000, we're now at 142200-ish. Another few days.

Proposed changes to bankstats page:



I didn't think any of this was wired up, you just have to push the button and wait 5-10 secs. We need to get all this stuff working properly. Reported market cap is a bit optimistic right now.  

They get paid for being full nodes on fast connections, posting collateral and participating in the consensus mechanism.    Anyway, above my pay grade.

Proposed change to block browser page:



One result batch at a time, looks a bit neater IMO...?

I don't understand why there needs to be any hashing at all. If the txes in the block are judged valid by consensus - and any conflicting double-spend attempts etc are rejected - then once that quorum is reached can the block not be simply added to the permanent chain? This should be a pretty quick process, set to run every x seconds.

I'll get around to understanding this stuff better eventually...

WRT your propositions though, if BNs were elected to do what was needed in strict succession, ie. with 100 BNs each one would process each 100th (101st, whatever)  block - would that help/solve the issue? Right now BNs get paid more or less at random it seems and it evens out over time; SPR had what seemed like a very reliable blockchain based voting system for BN payments, could something like that be employed?

What bitcreditscc said, and blockchain security via SmartSig: only BN's (or various collateralised node classes) will be validating transactions and baking them into the chain for distribution to all, in a non competitive manner. The more nodes we have doing this, the more resilient our blockchain. And having a collateral cost associated with running such a node provides an additional financial barrier to attempted chain vandalism. And for their service, nodes get paid.

Conventional PoW, as well as being monumentally wasteful, doesn't even provide very good security, as all PoW currencies funnel their hash through a very limited number of pools, thus short circuiting the whole point of a supposedly distributed system.

There is not a single PoW currency that 'relies' on pooled mining that I could not fuck up beyond all recognition with control of at most 3 pool servers. That's not security, it's a liability.

Try explaining to Jo Public why your PoW currency has any value with, "Because I spent a shitload of money on electricity producing these 1's and 0's!" ... then try again with, "Because it's backed directly by the money you spent buying it, and you can see all these assets that you now own a part of right in the wallet."

With every token minted, all other cryptocurrencies undergo inflation - the value declines. With BCR, every coin minted and purchased makes everyone's BCR worth more.

We could get trippier... ? 

Yes. You'll need 5 different daemons running with different datadirs, or 5 separate users running a daemon.

Still only need one IP as you can specify any port you want for each. And we know IPv6 works, maybe whoever runs that BN could write a tutorial...?

One of the things that I always wanted with Darkcoin was the ability to set a requirement that the client would not display your balance or transaction history without you entering a password, or pin number, or screen gesture, or something. Your wallet.dat shouldn't even betray your addresses... Obsessing over Darksend obfuscation of your transactions while any wandering vagabond could swipe a copy of your wallet.dat and see everything you'd been up to seemed a bit daft for a privacy-centric currency to me, so I'm going to try to implement this as an option for BCR.  

Working on a vanilla (mostly, I do like a splash of orange) theme for any aesthetic degenerates who don't love and adore the dark grey one.



This will also make it a lot easier to build future themes from, the stylesheet file is getting a lot more organised.

edit: new pic with added border and revised logo that'll work with both the light and dark themes currently extant.

The Momentum algo in action! When it's all shifted to BNs this will be a thing of the past hopefully. Should be just a steady (very minimal) hashrate without much delta.

OK, my live theme picker was throwing segfaults if you changed the theme more than once in a session and I couldn't figure out why, so I have gone with the "stick a theme=/path/to/your/beautiful/stylesheet.qss line in your bitcredit.conf file" approach instead.

Which incidentally is a far more efficient way of doing things in a number of ways. Also knowing how to do this will be really handy for future mischief.

For people who are afraid to edit a textfile, tough.

In action:
Currently for debugging purposes, if a "theme=/your/beautiful/theme.qss" line exists in bitcredit.conf, you get a popup telling you you're about to load a nonstandard theme and to have a vomit-bag ready:



It then gets loaded. Remember, the user agreed to it!
(apologies, testing purposes only remember...)



Total overhead = about ten more lines of code. And some lost breakfast.  

If there's no 'theme=blah' line in the conf file it loads the default Serious-Grey-With-Orangey-Bits one. No idea if the client will automagically handle Windows pathing with \ instead of / but I suppose we'll find out.