Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 136. (Read 284545 times)

Oh that's gorgeous lonecrouton. What colour is that, puce?

Select Your Own 'Orrible Theme 'feature' now fully working!

Use at your own risk, may induce dizziness, nausea and rage...   

Just some food for thought, here's our competition: https://bitreserve.org/en/homepage

I'm looking forward to putting our in-wallet version of this together: https://bitreserve.org/en/status  

We can beat them primarily on decentralisation and therefore security, privacy and no signup crap. Downloading the BCR wallet should be it.

Oh, and BCR reserves will belong to everyone with BCR, not just the parent company, and that's an ongoing revenue stream...  

Sorry if the git is confusing at the moment.

let me guide

Current branch (Master plus immediate update material)
0.30.16.8 --> WIP (Current branch + Meganet + IBTP)
0.30.16.8-+_elements --> WIP WIP ( 0.30.16.8+ elements)
0.30.16.8 -+-coinspark (0.30.16.8-+_elements + colored coins)
0.30.16.8 -+-FIX (0.30.16.8 -+-coinspark + nothing new yet)

These will be the basis of 0.30.17 which will be the major version update which all previous updates would have cumulatively contributed to it.

I agree with the incremental updates some of the easier stuff has already been done. 0.30.16.8b is the most current branch. This will be released without IBTP in a few hours after hack_ and thelonecrouton confirm that it is working.

This update reduces base Bn cost down to 50K at block 145000, it also lays in the ground work for block bidding and future separation of BNs.
It features many other updates, and i will write a changelog for it with the last push to the public master branch of the git. Also you will start to see branding being replaced by that of the company.

Great work with the GUI, we are nearly there !!!

Having a gander at the recent commits now, still mostly Klingon to me... 

No disrespect to bitcreditscc, but I think the updates will be incremental anyway, some pretty hefty changes suggested recently, they aren't all going to get released in one giant and fully functional upgrade.

Also, halfway there with the 'pick your own ugly paint job' thing:

Finding these themes will be an exercise left entirely to the user.    However, you have a choice of having the browser point at and only at a specific directory as above (eg. ~/.bitcredit/themes) or allowing the user to roam free and try to load christ knows what...

...which would mean I'd probably have to add some 'is this actually a valid css/qss file' code to prevent complications when someone tried to load an .mp3 or a .pdf or something. I would prefer the former, we could ship additional themes as they got tested for actual usability.

Yes please , thank you.

I have a developer background, although it's mostly based on front-end web development. I could still have a look at the code, won't hurt I guess.

Thanks for the guide, will take a look at it.

 well i keep trying to think on the roll out, the code looks great, bu how about phasing the updates so we can see how it all works out and instead of a shock change we slowly phase things in?

I see you have figured how to add live bids to the blocks (great work), but how about we have a scedule of changes and each in a different release?

This allows people to experience the changes slowly and also gets the nay sayers time to see the advantages and get them aboard before the complete PoW shift.

@thelonecrouton, do you agree ? Great work btw i built the new branch and can see all the work you've put in.

@bitcreditscc , can we have multiple stylesheets? maybe have a option to switch between one that a person likes?

had a chance to read further into the Elements thing? I just pushed a branch you can play with, 0.30.16.8b it's the master branch + Mining changes (60% done) need to just write the verification code.

I need time off from writing new stuff so i am completing the BCR- Elements branch as a curiosity project.

Any of the DASH guides will also do as a reference, but BCR doesn't have the fixed IP + port 9999 restriction. You can specify any port you want with a 'port=xxxx' line in your bitcredit.conf file(s) - you might also need to tick the 'Map port using UPnP' box under Options > Network if you're launching them from your local QT client.

All good, for now i actually need people who can review the changes i made to the code and people who can argue for/against them. As a human being i can make mistakes in both reasoning and coding so a different view is always welcomed and appreciated.

For now use this http://bitcredit.wikia.com/wiki/Bitcredit_Wiki

It will be updated when the new rules go live.

I see, thanks for the explanation! Currently in the process of obtaining my 5th BN (per 50k BCR). If there's anything I can do to help testing feel free to PM me!

Any guide available on how to setup a BN?

thanks, in a few days we will release a test version that addresses many of the developments discussed here. A Bank node is going down to 50K , so be sure to check in again soon

Right now 250000 but in the near future 50000. Need more BN's as tx validation is being moved to them..

I've been following the development for a while now. Keep it up, you guys are doing a great job!

Perhaps too early to ask, but what's the required BCR to start a node? Any final decisions made on this topic yet?

bitcredit-qt (stripped) from my latest build is 12.6MB, 7zip gets it to 3.5MB, rar 3.8MB, various tar flavours about 5MB. We can at least save on 'shipping weight' if needed.

A compressed blockchain probably wouldn't hurt either, eventually, though it's not a pressing concern.

For masternodes, there is no real purpose, but as you know we have branched off into an area which requires customers to have info on the entity they are transacting with, be it a bank or company.This list will be expanded by details such as assets issued and the (active) will serve as a means to tell if assets issued by the bn are still valid, ie if the collateral for the assets is moved, they are immediately frozen and and alert is sent to all wallets that have the asset (part of the mechanisms I am trying to put in for anti-fraud)

In it's current state, it just serves the purpose of letting a user know as much about the network as possible without having to move between browser and client. Eventually it's role will become very important to the average user, for example if you wish to do business with an entity on the chain  (once i figure out how the BN alias system), Their actual company name will appear in the list , and drawing from a regularly updated local database, i wish to make sending BCR/Assets as easy as sending a message on whatsapp. Simply select BN name, select amount , send.

My one fear is that after we have all that we need + the over simplification of processes, the client potentially could be 50 MB+.

We'll need a lot of time to optimize the code. But we'll be leaps and bounds ahead of the pack.

I'm waiting to try it in the future when all the tests pass.