@Fonneda do you mean the total supply?
There is no total supply, it is uncapped.

I started to write the API documentation here: https://github.com/UBIC-repo/Documentation/blob/master/API.md

For every API call you need to send the "apiKey" as header parameter.
The API calls are handled in REST/ApiServer.cpp with the method std::string ApiServer::route(std::vector<std::string> urlParts, std::string jsonPost)
I'll add some documentation soon.

@uboid when I sent you the transaction I found an issue with the nonce counter.
I'll try to fix it ASAP and give you new instructions then on what to do with your nodes.
Sorry for this.

@uboid thank you, if you post one of your addresses I will make you a donation for this.

In order to update your node regarding the previous statement delete old UBIC files:

Then run the installation again:

Sadly I found a serious error in the code and because very few people seem to use UBIC as of today I will stop minting and restart with a new genesis block in the next days.

Update: Luckily the problem was fixed without the need of starting again from the genesis.

There are still no nodes.
Do you intend to run a node? If so you can publish your IP address and I will add to the node list.
You will then start receiving blocks.

@uboid may be you can try to rebuild openssl, then build UBIC again.

1.58 is too old, 1.6x is required.
Can you try to install a newer version from the sources?

This will install 1.64:

@uboid can you run apt-cache policy libboost-all-dev and give me the output?

We now also have our own sub reddit: https://www.reddit.com/r/UBIC/

@regarcigar I understand that the details are not that easy to understand because it goes very technical, less technical descriptions will be released later.
We are also still working on the Windows wallet which will be released during the next days so that less technical people can join.

@vuppie0 so it certainly is. However the DSCs(Document Signing Certificates) still needs to be published on the ICAO PKD web site to be used in UBIC.
Link: https://pkddownloadsg.icao.int/

@vuppie0 : Expanding to other countries is possible.
The requirement are that the country:
 - uses ECDSA certificates or RSA certificates with an exponent >= 65537
 - emits a new Document Signing Certificate at least every three months are required by the ICAO
 - Publishes these certificates
This was the case with the countries listed in my first post.

UBIC has been released: https://bitcointalk.org/index.php?topic=3021063.0

UBIC stands for Universal Basic Income Currency and is a blockchain -based platform that distributes crypto currency under the form of a universal basic income .
- How does it work?
Since 2008, more than 60 countries issue biometric passports, which include a NFC-compliant RFID chip containing digitally signed personal information.
These embedded NFC chips can be read out easily using smartphones and other NFC-capable devices.
UBIC takes advantage of this existing technology and uses the unique digital signature issued with every E-Passport in order to securely distribute a basic income.
To receive this UBI, a user has to recover the digital signature from the chip by using his NFC capable computer or smartphone, this piece of information is then cryptographically linked to an UBIC address.
Within minutes— and this every minute until approximately expiration of his passport— the user will receive a country -specific UBIC token named UUS for the US, UCH for Switzerland, UUK for the UK, and so on.

-Who can participate?
Everyone  can receive and make payments, however, if you want to receive an UBI, you need to own a valid (non-expired) passport of one of the following countries:

Currency code	Country	UBI yearly emission rate	additional information
UCH	Switzerland	10,196,640
UDE	Germany	100,599,840
UAT	Austria	10,617,120	passports after October 2014
UUK	United Kingdom	79,838,640
UIE	Ireland	5,781,600	passports after May 2016
UUS	USA	393,096,240
UAU	Australia	29,223,360
UCN	China	1,677,767,760	Hong Kong passports after July 2019
USE	Sweden	12,036,240
UFR	France	81,730,800
UCA	Canada	44,150,400
UJP	Japan	154,526,400	passports after May 2016
UTH	Thailand	81,520,560
UNZ	New Zealand	5,571,360
UAE	United Arab Emirates	11,300,400
UFI	Finland	6,675,120
ULU	Luxemburg	525,600
USG	Singapore	6,832,800
UHU	Hungary	11,931,120
UCZ	Czech Republic	12,877,200
UMY	Malaysia	38,684,160
UUA	Ukraine	54,767,520
UEE	Estonia	1,681,920	No registration possible yet
UMC	Monaco	52,560	No registration possible yet
ULI	Liechtenstein	52,560	No registration possible yet
UIS	Iceland	420,480	passports after february 2013
UHK	Hong Kong	8,988,000	No registration possible yet
UES	Spain	56,764,800	passports after July 2016

- How much will I receive?
There is a static amount of coins distributed every minute. For example, for Germany, 191 units will be minted every minute.
The amount each individual receives depends on the amount of people having registered. If there is only one UBI subscriber for Germany, then he will collect the full 191 units.
If there are more than one subscriber, this amount will be equally split and if there is a division reminder, it will be added to the payout of the next block.
As a consequence, if the number of subscribers increase, you'll receive less but probably more valuable coins.
This design incites people to register as soon as possible and makes the coins valuable, as the maximal supply is predictable and the value of a single coin has the potential to increase over time.

- What about transaction fees?
Transaction fees are important to ensure that a fair use is made of the limited available amount of transaction storage within a block.
To make sure this fee isn't neither too low nor too high, the fee will depend on the current UBI payout.
This means that a simple one input, one output transaction will cost you about 3 to 6 hours of UBI. The transaction fee itself is burned/destroyed, which is meant to reduce inflation.

- How many people can join?
UBIC intends to be much more scalable than other crypto currencies, this will mainly be achieved by relying on less but more powerful nodes;
by design, donations to nodes have been simplified at some of the dev funds will be allocated to it.
with a mix of designated and elected delegates.
Under the current implementation, there will be a maximum of 51 super nodes.
Currently, blocks are limited to about 2MB in size; this translates in about 20 times more block space than Bitcoin currently has.

- When will it start?
The source code is released hereby on Github as well as all the necessary resources to run a node.

- External resources
White paper
Android app
Source code
Block explorer
Installation instructions (Linux)
Installation instructions (video)


- Development fund
UBIC is the result of over one year of intense research and development, this effort won’t stop now and will require some funding.
Unlike many other projects, we have decided not to run an ICO, instead, our development fund will get its own kind of UBI.

The development fund will be used for expenses such as:
 - Continuing the development of UBIC
 - Bug, translation and security bounties
 - Blockchain explorer development
 - Mobile App development
 - Running nodes
 - And any required or desirable new developments.

If you want to do one of those things, please write to me.
If you want to receive donations for running a node, all you need to do is to add your address in the config.ini file.
Then create a Pull request with your node IP address on this repository: https://github.com/UBIC-repo/node-list

- Roadmap

2018, Q1
 - Release UBIC v0.1 (done)
 - Release a white paper (done)
 - Release a blockchain explorer (done)

2018, Q2
 - Release a mobile app (done)

2018, Q3
 - Integrate a KYC functionality to the mobile app.(Halfway)

2020-2021
 - Release an E-voting solution on top of UBIC
 - Use the E-Voting solution to elect validators

- Donations
All currencies/tokens send to this addresses will be included to the development fund:
 - UBIC:    qYReFGX7dKkoKCp2nej7EyW6KRSb7QAti
 - Bitcoin: 13sFUA2GPeFqvACxzYKHVrqXaXKc1uw9fv

People would get cryptocoins for registering their passport using their smartphone. On the play store you can already find apps for reading out the content of the Passport NFC chip, some with over 50,000 installs.
In the case of UBIC there would be no personal information shared on the Blockchain. The registration transaction will only contain the hash of the passport data and a non-transferable proof of signature knowledge, in the case of ECDSA 256bits this is less than 128bytes.
However it is true that the holder of an address that was verified against a passport should be aware that the country issuing his passport has the ability to find out about it.
UBIC isn't Zcash!

It is also true that in the case of UBIC you'll always have a single point of failure which is the government who could issue malicious signatures. However it is very unlikely that countries like Switzerland, Germany, Austria or the UK take such a decision.
It would be very risky for them as their Document Signing Certificates or Country Signing Certificates could get revoked by other countries or the ICAO for such a behavior. So if a government is against such a currency it is much more advantageous for them to just use a law to ban it, but this could also happen to Bitcoin.

EDIT: this is the announcement thread: https://bitcointalk.org/index.php?topic=3021063.20
This is a Pre-announcement for a cryptocurrency that is still in development and that aims to distribute it's monetary units following a universal basic income scheme.
Every individual that successfully verifies his passport using NFC technology will be granted a small reward in each block that is issued on the UBIC blockchain.
Such a procedure can be done easily using almost every recent smartphone.
At least two other projects are already trying to implement a similar currency system. However they both rely on a web of trust to prevent sybil atacks.

There are currently 3 solutions that are explored in the crypto community to solve this kind of attack:
 - The web of trust as used by Circles and Duniter
 - Proof-of-Individuality tokens as described by Johan Nygren
 - Using the the digital signature contained on every biometric passport as suggested by Mike Hearn

All of them have their downsides but I believe the passport solution is the more practical and the most secure one. I've already achieved to implement it in C++ by using a non-transferable proof of signature knowledge. This kind of proof can be computed on both ECDSA and RSA signatures and is much smaller and faster to verify than SNARK.
However because the non-transferable proof of signature for RSA is "hackier" than the one for ECDSA  the first versions of UBIC will only support ECDSA signatures meaning that it can only be used by individuals holding following passports:
 - Switzerland all valid passports
 - Germany all valid passports
 - Austria all passports issued after 2014
 - United Kingdom all passports issued after 2016
 - United Arab Emirates all valid passports

Brazil also uses ECDSA but doesn't issue a new Document Signing Certificate every 3 months as required by the ICAO. This is why there is no way for UBIC to estimate when the passport was issued and if it already expired.

To make it as fair as possible there will be one currency for each country but running on the same Blockchain. If you hold a Swiss passport you will get some UCH the swiss unit for the UBIC, if you are German you will get some UDE and so on..
A vast majority of the monetary supply should be distributed to the end users. Much smaller shares will be allocated as rewards for securing the network and development.
To give the currency value and avoid hyperinflation the supply increase will be constant with perhaps a little increase about 0.2 - 0.5% every year. Monetary units will be distributed on a continuous basis. The end user reward will be shared like a Pie, if the end user reward for a block is 100MU and there are 5 users each will get 20MU, if there are 100 users each will get 1MU and so on.
There shall be no premine.

Consensus could be achieved through POW or proof of something else. Nothing's Carved in Stone.

If you want to contribute just send me a private message, I appreciate any help.
In the following weeks I'll start to make the current work available on Github at: https://github.com/ubicorn

Not sure if you were talking about my idea but I address the life cost difference problem between different region by having one currency for each country.