Vivokey Spark - Datasheet and APIs


#1

Hello all!

I was curious if there was any data sheets for the vivokey spark. I was also hoping to find more information on the AES128 functionality of the device. Can you encrypt the data stored in the NDEF records? If not, what is the expected use case? I understand that the vivokey spark is a bit more plug and play than the xNT, but was also wondering if you can interact with the device on a lower level like the xNT.

I am really looking forward to receiving my new vivokey spark and writing apps against the APIs that you guys are planning on releasing.

I can also send you guys an email requesting the same info if preferred.

Thanks!
M


#2

First I want to say that it’s totally my fault for not preparing proper documentation for the Spark and VivoKey service platform before the Spark was released. We had several units shipped to various people early to prep them for launch and they ended up being implanted into people and then questions started flying so we went ahead and released the Spark and MVP version of the VivoKey service platform ahead of any documentation.

The chip in the Spark is an ICODE ISO15693 NFC Type 5 compliant chip.

The NDEF data of the Spark is pre-programmed with a unique Spark URL that directs to the VivoKey service platform. This URL is central to the function of the VivoKey profile service, is locked, and cannot be changed or written to. The AES function performs encryption in the chip. We pre-program AES keys into the Spark and these are used to authenticate the Spark to the VivoKey service platform. When you create a VivoKey profile, your Spark is linked to it cryptographically using those keys. The only way to access your profile or any services tied to it will be by scanning a chip that is associated with your profile. It is not possible at this time for customers to access or use those keys.

That’s great! The point of the Spark and VivoKey service platform is to keep expanding the utility of your implant! The APIs, bug fixes, and more platform features are due out in the next release of the app. I really can’t wait to see what developers create!


Vivokey Spark for Novice
#3

Thank you so much Amal for the info and quick response.

Bummer that the records aren’t editable, but I totally understand it with the plug and play concept for customers since it ties into the vivokey platform.

I love the work that you guys do and I can’t wait to see the platform and company grow!

Also can’t wait until the flex one leaves beta! Super excited for it.

Thanks again!
M


#4

The goal is to basically make it just as functional on the NDEF side of things as an xNT might be, but all managed by the platform instead of having people fuss with writing data to it. The only limitation we can see at this point is creating custom data types for applications like on-phone task manager triggers, etc… but honestly, that’s more useful for adhesive stickers you place in cars and in the home to automate various mobile tasks… but even so, we may create a hook for the VivoKey app to perform tasks on the user’s phone upon scan while leaving the operation of sharing profile data or redirecting to a URL still functional for 3rd party scanners (other people’s phones)… so I guess in that way we will be able to do more than an xNT… huh… cool.

It’s growth will be fueled by people like you, so thank you!

Snag after snag keep holding us back, but it’s progressing… slowly. The VivoKey Flex One will allow all the functionality with the VivoKey platform as well as autonomous operation if you want to leverage isolated OTP key storage and code generation, U2F, PGP, etc. … I hope the current issues we face will be mitigated soon and we can move the Flex One to public beta soon.


#5

Hey Amal,

One more question if you don’t mind.

I just received my spark and I noticed that this time there was an xLED HF box was packaged inside the plastic bag along with the rest of sterilized products (gauze pad, chloraprep, bandage, etc.). should I have any concern about how sterile the rest of the products are in the bag due to this?

It’s obviously still packaged outside of the injector but within the same overall bag as everything else that contains the materials required to safely perform the injection.

Also as a side note, it was not listed as being included on the spark page description nor was it an additional purchase that I made.

Thank you again!

Respectfully,
M


#6

It is ok. The poly bag is meant to keep finger oils and physical perforation from affecting the injector pouch.

Correct… we made a recent change to the goodies included. Thanks for the reminder, I’ll update the product page.


#7

Thanks for the info! Just wanted to double check. :slightly_smiling_face:


#8

Here’s a link to the public short data sheet for the ICODE chip that the Spark uses. There are a few different ICODE models, but only the ICODE DNA supports AES Encryption, so pretty sure this is the right one.

The full data sheet and the programming documentation (with the APDU commands) are not publicly available.