Identity verification - Revision history

Slackjore: /* External links */ added new link

2019-04-10T17:00:18Z

‎External links: added new link

Slackjore: updated name

2019-01-20T18:40:46Z

updated name

Punqtured: 10 revisions imported

2019-01-19T22:20:01Z

10 revisions imported

Slackjore: /* How to use */ added section for smart voucher use

2018-10-16T15:54:45Z

‎How to use: added section for smart voucher use

Slackjore: added first line

2018-10-15T12:39:43Z

added first line

Slackjore: /* Numbers */ updated link to byteball.co

2018-09-24T11:21:36Z

‎Numbers: updated link to byteball.co

Slackjore: added revised terms of reward

2018-06-16T13:17:01Z

added revised terms of reward

Slackjore: added paragraph on using one's own device

2018-05-30T16:04:30Z

added paragraph on using one's own device

Slackjore: added "back-up device" section

2018-05-29T22:39:17Z

added "back-up device" section

Slackjore: added section: practise!

2018-05-08T10:57:05Z

added section: practise!

@@ Line 49: / Line 49: @@
 *https://www.jumio.com/about/press-releases/byteball-ico-identity-layer/
 *http://finovate.com/jumio-partners-byteball-bring-kyc-ico-issuers/
 == References ==

@@ Line 1: / Line 1: @@
 This page is about Real Name Attestation.
-Starting 18 January 2018, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>
+Starting 18 January 2018, every Obyte user can link his Obyte address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Obyte wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>
-This attestation allows the user to prove to anybody that his Byteball address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.
+This attestation allows the user to prove to anybody that his Obyte address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.
 ==How to use==
-Install the [[Chatbot#Real_name_attestation_bot|Real name attestation bot]] from the Bot Store in a '''Single-Address Wallet''', and follow ALL the instructions. After first successful verification, you are rewarded with $12.00 worth of Bytes from the distribution fund. The $12 attestation reward, which was previously paid directly, is now [after 15 June 2018] paid to a [[smart contract]] instead, allowing the user to withdraw the funds exactly 12 months from the time of attestation. To prevent funds from getting stuck forever, the contract will have a second time-lock ensuring that if the funds haven’t been claimed after two years, they will be transferred to the [[Byteball_community_fund|Community Fund]].<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-episode-ii-29b6f1cd4ecc</ref>
+Install the [[Chatbot#Real_name_attestation_bot|Real name attestation bot]] from the Bot Store in a '''Single-Address Wallet''', and follow ALL the instructions. After first successful verification, you are rewarded with $12.00 worth of Bytes from the distribution fund. The $12 attestation reward, which was previously paid directly, is now [after 15 June 2018] paid to a [[smart contract]] instead, allowing the user to withdraw the funds exactly 12 months from the time of attestation. To prevent funds from getting stuck forever, the contract will have a second time-lock ensuring that if the funds haven’t been claimed after two years, they will be transferred to the [[Obyte_community_fund|Community Fund]].<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-episode-ii-29b6f1cd4ecc</ref>
 Only perform the ID attestation inside your OWN device (phone or computer). If someone else is providing the funds for this in order to get a [[Referral]] reward, there must be two separate devices used for this to be paid.
@@ Line 44: / Line 44: @@
 ==Numbers==
-See how many Byteball verifications are done [https://byteball.co/attestors here] (real name attestor).
+See how many Obyte verifications are done [https://obyte.io/attestors here] (real name attestor).
 == External links ==

← Older revision		Revision as of 15:54, 16 October 2018
Line 9:		Line 9:

	Only perform the ID attestation inside your OWN device (phone or computer). If someone else is providing the funds for this in order to get a [[Referral]] reward, there must be two separate devices used for this to be paid.		Only perform the ID attestation inside your OWN device (phone or computer). If someone else is providing the funds for this in order to get a [[Referral]] reward, there must be two separate devices used for this to be paid.
		+
		+	===Smart voucher===
		+	After entering your address in the bot chat, and selecting <code>private</code> or <code>public</code> for the attestation, the bot will provide a wallet link to pay <code>0.xxxxxxxx GB</code> ($8 in Bytes) or to enter the code if you have a [[Smart_Voucher\|smart voucher]].

	===Exact amount===		===Exact amount===

← Older revision		Revision as of 12:39, 15 October 2018
Line 1:		Line 1:
		+	This page is about Real Name Attestation.
		+
	Starting 18 January 2018, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>		Starting 18 January 2018, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>

@@ Line 39: / Line 39: @@
 ==Numbers==
-See how many Byteball verifications are done [https://byteball.fr/heartbeat.php here] (next-to-last two lines of "12 hour snapshot").
+See how many Byteball verifications are done [https://byteball.co/attestors here] (real name attestor).
 == External links ==

← Older revision	Revision as of 22:20, 19 January 2019
(No difference)

@@ Line 1: / Line 1: @@
-Starting 18 January, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>
+Starting 18 January 2018, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>
 This attestation allows the user to prove to anybody that his Byteball address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.
 ==How to use==
-Install the [[Chatbot#Real_name_attestation_bot|Real name attestation bot]] from the Bot Store in a '''Single-Address Wallet''', and follow ALL the instructions. After first successful verification, you are rewarded with $20.00 worth of Bytes from the distribution fund.
+Install the [[Chatbot#Real_name_attestation_bot|Real name attestation bot]] from the Bot Store in a '''Single-Address Wallet''', and follow ALL the instructions. After first successful verification, you are rewarded with $12.00 worth of Bytes from the distribution fund. The $12 attestation reward, which was previously paid directly, is now [after 15 June 2018] paid to a [[smart contract]] instead, allowing the user to withdraw the funds exactly 12 months from the time of attestation. To prevent funds from getting stuck forever, the contract will have a second time-lock ensuring that if the funds haven’t been claimed after two years, they will be transferred to the [[Byteball_community_fund|Community Fund]].<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-episode-ii-29b6f1cd4ecc</ref>
 Only perform the ID attestation inside your OWN device (phone or computer). If someone else is providing the funds for this in order to get a [[Referral]] reward, there must be two separate devices used for this to be paid.
@@ Line 33: / Line 33: @@
 ===More than one verified address===
-There is no way to remove an attestation (maybe the device was lost) but users can attest their new BB address. Then there will be (at least) 2 attestations of the same user. Tony would expect service providers to check if a later attestation of the same user exists, and if it does, not to trust the old one.<ref>https://www.reddit.com/r/ByteBall/comments/7rpsmn/jumio_verification_and_comprised_private_keys</ref>
+There is no way to remove an attestation (maybe the device was lost) but users can attest their new BB address. Then there will be (at least) two attestations of the same user. Tony would expect service providers to check if a later attestation of the same user exists, and if it does, not to trust the old one.<ref>https://www.reddit.com/r/ByteBall/comments/7rpsmn/jumio_verification_and_comprised_private_keys</ref>
 ===Referral rewards===

@@ Line 14: / Line 14: @@
 ===Webcams===
 Use your Android camera if possible. Sometimes it is tricky to get webcam ID images big enough and in focus.
 ===Practise!===