$0.056-2.63%
Rosling DataRosling Data

Keeta Bivo Anchor CA

Certificatevalid

issued to keeta_aab6qmfh…qrhq

Validity

Status
valid
Valid from
Valid until
Term
10 years

Validity

A certificate holds from Valid from to Valid until: the two moments its issuer wrote into it.

Valid
Now lies between the two, and the holder has not taken it off.
Expired
Valid until has passed. It stays on the account until the holder takes it off.
Taken off
The holder removed it from its account.
Term
How long it was issued for.

On the ledger

Added
· 2 mo after Valid from
Block
a72c5737c8…1b86

On the ledger

A certificate is not a transfer: its holder adds it to its own account with a MANAGE_CERTIFICATE operation, in a block on its own chain, and takes it off the same way. It can only go on the account whose key it names.

Added
The moment the network settled the block that added it. Valid from is the issuer's own moment, written into the certificate.
Taken off
The moment the network settled the block that took it off.
Block
The block that added it, or took it off.
Replaces, Replaced by
The holder's certificate from the same authority added just before or just after this one. A renewal mostly adds the new one and takes the old one off within the hour.

Issuer

Provider
Keeta Bivo Anchor CAproviders bivo, bivo-anchor-v2.keeta.com, bivo-anchor.keeta.com
Root
Keeta Bivo Anchor CA ✓in the permissions of 9 tokens
Issued
272 certificates

Issuer

Provider
The issuer as the certificate names it, in its issuer field; where that is an account's address, the name the account goes by. Under it, the services page's providers behind it, where it names any.
Root
The certificate at the top of its chain, and where it is published: in the registry the network points at, in a provider's own document on the chain, or in a token's permissions. Published nowhere else: only the block carried it. Anyone may issue under a root of their own; which roots a token or an app accepts is its own choice.
Issued
Every certificate added under this issuer, to any account.

Access

Tokens
The ledger lets the holder do this while the certificate is valid and on its account, under Keeta Bivo Anchor CA:

Access

What holding this certificate opens, as the ledger and the documents state it. Nothing here is judged by this site: a new token, service or issuer shows up as soon as one names it.

Tokens
A token's permissions can give a right to whoever holds a valid certificate under a given certificate. The ledger checks it on every send, for the sender and the recipient, with only the certificates the holder added it with.
Services
A service's document can name the issuers whose certificates it accepts. It names them by name, without a key, so each service checks the key itself.
Ask for KYC
Anchors whose document asks for KYC but names no issuer: which certificates they accept, they do not say.

Attributes

No attributes.

no attributes

Attributes

What the issuer states about the holder, one attribute each: a name, a date of birth, an e-mail address, a document; for an organization its legal name, its registration and its owners.

***
A sealed attribute: encrypted for the holder, so the certificate carries it without anyone else being able to read it.
A value
An attribute in the clear: anyone can read it.

Chain

  1. This certificateissued by itself: the root · until · ✓

✓ Every signature holds, up to a root. · checked

Chain

From this certificate up to a root: each step is issued by the next. The archive checks every signature with Keeta's own software.

Carried in the block
The block brought this certificate along with the one it added.
Published
Not carried, but found where it is published: the registry the network points at, a provider's own document, a token's permissions.
Not carried, not published
Only its name is known: the name the step below gives for its issuer.
✓
The signature holds: the issuer's key made it.
✗
A certificate of the issuer's name is known, and its key did not make the signature.
–
The issuer's certificate is not known, so the signature cannot be checked.

Identifiers

Hash
FAF61B1321F8A9E849243C59E1612AD55CA2F60111B6823C5B1F21EB6B44D6AE
Serial
0x1
Subject key id
6FC26B08119AA3A5124B02DBE67D7DCD3349032B
Authority key id
6FC26B08119AA3A5124B02DBE67D7DCD3349032B
Key usage
cRLSign, keyCertSign, nonRepudiation, digitalSignature

Identifiers

Hash
The name the ledger gives the certificate, and its address on this site.
Serial
The issuer's own number for it.
Subject key id
Names the holder's key.
Authority key id
Names the key of the authority that issued it, as the certificate states it.
Key usage
What the holder's key may be used for with it.

Bytes

Certificate (PEM)
-----BEGIN CERTIFICATE-----
MIIBbjCCARSgAwIBAgIBATALBglghkgBZQMEAwowHzEdMBsGA1UEAxMUS2VldGEg
Qml2byBBbmNob3IgQ0EwHhcNMjYwMzI1MTQ1MDAwWhcNMzYwMzI1MTQ1MDAwWjAf
MR0wGwYDVQQDExRLZWV0YSBCaXZvIEFuY2hvciBDQTA2MBAGByqGSM49AgEGBSuB
BAAKAyIAA+gwp2sP/6vvI2d6HJPtG91lpo4muy/ZWJDMciEfxQ7eo2MwYTAPBgNV
HRMBAf8EBTADAQH/MA4GA1UdDwEB/wQEAwIAxjAfBgNVHSMEGDAWgBRvwmsIEZqj
pRJLAtvmfX3NM0kDKzAdBgNVHQ4EFgQUb8JrCBGao6USSwLb5n19zTNJAyswCwYJ
YIZIAWUDBAMKA0cAMEQCIH/O/b9Y0DGTL9iCByq8QM2abgVEWQg/J4URZa/CCATc
AiA3Zbxr3J8Dg7CPPv4JjAbKC/b1HnkgVYEPu03PyKTnyg==
-----END CERTIFICATE-----

Search

Settings

Theme
Values in
Dates and times
Time zone
Primary username service
Dust and spam