I added the fee table and I hope the calculation is correct.
https://ubic.network/fees/
Topic: [ANN] UBIC:The cryptocurrency providing UBI for the masses using the E-Passport - page 7. (Read 18227 times)
May 23, 2018, 10:23:02 AM
May 22, 2018, 03:12:57 AM
Thank you. I will try it out.
May 21, 2018, 04:03:48 PM
I added the /kyc endpoint. It currently only supports anonymous authentication and is "untested".
The request to the endpoint is a base64 string of the following serialized structure:
Anonymous authentication is mode 0 and the fields ldsHashes, dg1 and dg2 remain empty.
Once submitted and if matching to a genuine UBIC identity the response is something like this:
The request to the endpoint is a base64 string of the following serialized structure:
Code:
struct KycRequestScript {
uint8_t mode;
std::vector passportHash;
std::vector addressPublicKey;
std::vector challenge;
std::vector challengeSignature;
std::vector ldsHashes;
std::vector dg1; // written information
std::vector dg2; // facial image
}
Anonymous authentication is mode 0 and the fields ldsHashes, dg1 and dg2 remain empty.
Once submitted and if matching to a genuine UBIC identity the response is something like this:
Code:
{
"success": true,
"dscID", "45f73ea89b9....";
"currencyID", 1;
"expiration": "1723966935",
"passportHash": "78eb67aa55de5..."
}
May 20, 2018, 03:39:24 PM
I want to improve the Block Explorer and am trying to create the mobile app. In both cases it would be very useful if there was an API call that would return the current transaction fee per byte. Can this be done? 
I added a new endpoint /fees it will return you something like this:
Code:
{
"description": "Fees for 1MB (1000 bytes)",
"fees": {
"1": "19400000",
"2": "191400000",
"3": "20200000",
"4": "151900000",
"5": "11000000",
"6": "747900000",
"7": "55600000",
"8": "3192100000",
"9": "22900000",
"10": "155500000",
"11": "84000000",
"12": "294000000",
"13": "155100000",
"14": "10600000",
"15": "21500000",
"16": "12700000",
"17": "1000000",
"18": "13000000",
"19": "22700000",
"20": "24500000",
"21": "73600000",
"22": "104200000",
"23": "3200000",
"24": "100000",
"25": "100000"
}
}
The numbers represent a currency by it's ID. The values are the fees for 1MB and expressed in base units.
So to get the fee per byte you have to calculate Value / (1000 * 1000000).
I am also trying to integrate a KYC endpoint but this will take a little bit more.
May 19, 2018, 02:26:57 PM
I want to improve the Block Explorer and am trying to create the mobile app. In both cases it would be very useful if there was an API call that would return the current transaction fee per byte. Can this be done?
May 17, 2018, 06:39:35 AM
I wonder what would happen if you would fork the narrative of ubic whitepaper with a second whitepaper presenting ubic mainly as future KYC-blockchain, which gives away utility-tokens for free to user to grow faster.
I will think about it. The KYC and E-Voting protocols could indeed deserve their own whitepaper.
What I currently have in mind regarding KYC is the following procedure:
- Using his smartphone the user scans a QR code that contains a URL + a challenge + a flag that indicates what data are needed.
- The user sees the domain where the information will be send and what will be send.
- The user scans the NFC chip of his passport again.
- The information are send to the URL given in the QR code.
- The UBIC core software is used to verify the KYC request.
From a more technical perspective:
- When registering your passport to get a UBI reward you publish your UBIC address, the signed hash of the passport and a non-transferable proof of signature for the signature on the passport hash.
- The signed hash is in fact the hash of the hashes for every "file" contained on the passport.
- There are 2 relevant "files" DG1 (the MRZ containing almost all written information) and DG2 (containing the facial image)
- So there could be 3 authentication modes:
- Anonymous (is used on the UBIC blockchain), it doesn't reveal any personal information.
- written information (Passport number, date of birth, date of expiry, document type, first name, last name).
- Facial image
- The verification is done by verifying that the hash of the personal information (DG1 or DG2) match with the signed passport hash. From there it is straightforward to verify that this signed hash match with the one of the UBI receiving address.
How do you imagine the utility token in context of KYC and voting? Does the KYC-Request burns a certain amount of tokens? For example your relative share of UBIC that you recieved within the last 100 Blocks?
KYC and e-voting don't have to necesserly take place on the blockchain. The blockchain is only required to verify that public key X is indeed a unique individual.
So there is no need to pay for these services.
May 16, 2018, 02:42:00 PM
There are many projects that want to provide KYC solutions. The two projects I have heard of are uPort and Civic, they are both relying on "identity validators", according to them those validators can be banks or other institutions.
I could imagine that UBIC could also become a validator in their system. What do you think?
I could imagine that UBIC could also become a validator in their system. What do you think?
Yes, UBIC could give a cool validator for a lot of projects. I wonder how people opposing the idea of basic income would react when they realize that they actually get payed for using ubic for KYC instead of having to pay.
May 16, 2018, 02:34:24 PM
I wonder what would happen if you would fork the narrative of ubic whitepaper with a second whitepaper presenting ubic mainly as future KYC-blockchain, which gives away utility-tokens for free to user to grow faster.
I will think about it. The KYC and E-Voting protocols could indeed deserve their own whitepaper.
What I currently have in mind regarding KYC is the following procedure:
- Using his smartphone the user scans a QR code that contains a URL + a challenge + a flag that indicates what data are needed.
- The user sees the domain where the information will be send and what will be send.
- The user scans the NFC chip of his passport again.
- The information are send to the URL given in the QR code.
- The UBIC core software is used to verify the KYC request.
From a more technical perspective:
- When registering your passport to get a UBI reward you publish your UBIC address, the signed hash of the passport and a non-transferable proof of signature for the signature on the passport hash.
- The signed hash is in fact the hash of the hashes for every "file" contained on the passport.
- There are 2 relevant "files" DG1 (the MRZ containing almost all written information) and DG2 (containing the facial image)
- So there could be 3 authentication modes:
- Anonymous (is used on the UBIC blockchain), it doesn't reveal any personal information.
- written information (Passport number, date of birth, date of expiry, document type, first name, last name).
- Facial image
- The verification is done by verifying that the hash of the personal information (DG1 or DG2) match with the signed passport hash. From there it is straightforward to verify that this signed hash match with the one of the UBI receiving address.
How do you imagine the utility token in context of KYC and voting? Does the KYC-Request burns a certain amount of tokens? For example your relative share of UBIC that you recieved within the last 100 Blocks?
May 16, 2018, 08:03:35 AM
There are many projects that want to provide KYC solutions. The two projects I have heard of are uPort and Civic, they are both relying on "identity validators", according to them those validators can be banks or other institutions.
I could imagine that UBIC could also become a validator in their system. What do you think?
I could imagine that UBIC could also become a validator in their system. What do you think?
May 16, 2018, 06:26:48 AM
I wonder what would happen if you would fork the narrative of ubic whitepaper with a second whitepaper presenting ubic mainly as future KYC-blockchain, which gives away utility-tokens for free to user to grow faster.
I will think about it. The KYC and E-Voting protocols could indeed deserve their own whitepaper.
What I currently have in mind regarding KYC is the following procedure:
- Using his smartphone the user scans a QR code that contains a URL + a challenge + a flag that indicates what data are needed.
- The user sees the domain where the information will be send and what will be send.
- The user scans the NFC chip of his passport again.
- The information are send to the URL given in the QR code.
- The UBIC core software is used to verify the KYC request.
From a more technical perspective:
- When registering your passport to get a UBI reward you publish your UBIC address, the signed hash of the passport and a non-transferable proof of signature for the signature on the passport hash.
- The signed hash is in fact the hash of the hashes for every "file" contained on the passport.
- There are 2 relevant "files" DG1 (the MRZ containing almost all written information) and DG2 (containing the facial image)
- So there could be 3 authentication modes:
- Anonymous (is used on the UBIC blockchain), it doesn't reveal any personal information.
- written information (Passport number, date of birth, date of expiry, document type, first name, last name).
- Facial image
- The verification is done by verifying that the hash of the personal information (DG1 or DG2) match with the signed passport hash. From there it is straightforward to verify that this signed hash match with the one of the UBI receiving address.
May 15, 2018, 05:59:38 PM
I wonder what would happen if you would fork the narrative of ubic whitepaper with a second whitepaper presenting ubic mainly as future KYC-blockchain, which gives away utility-tokens for free to user to grow faster.
May 10, 2018, 08:53:14 AM
I just added the Document Signing Certificates for March and April. Passports issued during these two months should work now.
May 09, 2018, 05:23:45 AM
Looks like a classical port scan. I don't think UBIC was targeted.
May 09, 2018, 04:16:26 AM
Wow, I had a look at the WARNING log file and looks like some people are already trying to steal some coins.
Code:
[WARNING 1523786429] (58471) Unallowed API request from IP:183.208.179.228
[WARNING 1523821586] (58471) Unallowed API request from IP:183.208.179.228
[WARNING 1524448885] (70549) Unallowed API request from IP:59.63.206.169
May 08, 2018, 04:28:31 PM
If you are using a firewall make sure that port 1334 is open or TCP connections.
This can be ensured by running:
Also your log files might getting huge.You can delete them by running:
This can be ensured by running:
Code:
sudo ufw allow 1334/tcp
Also your log files might getting huge.You can delete them by running:
Code:
sudo rm -rf /var/ubic/LOGS/*.txt
May 03, 2018, 06:29:05 AM
Do not have NFC usb scanner to register passport. Waiting for a mobile app.
From where are you from?
May 03, 2018, 06:23:57 AM
Do not have NFC usb scanner to register passport. Waiting for a mobile app.
May 03, 2018, 05:08:45 AM
Has some one else here already tried to register his passport?
May 03, 2018, 05:07:29 AM
Just after I registered my passport my SSD died, luckily it's still readable.
Where can I find my wallet keys to save then?
If you lose your keys is it possible to recover your coins using your passport?
Where can I find my wallet keys to save then?
If you lose your keys is it possible to recover your coins using your passport?
did you recover your wallet keys?
Yes
May 03, 2018, 03:59:34 AM
Just after I registered my passport my SSD died, luckily it's still readable.
Where can I find my wallet keys to save then?
If you lose your keys is it possible to recover your coins using your passport?
Where can I find my wallet keys to save then?
If you lose your keys is it possible to recover your coins using your passport?
did you recover your wallet keys?
Jump to: