One more "Which implant should I get and other dumb questions"

[Zwack]

@XEMON

So except those 3 (“Magic” 1K), all other HF chip will have to be enrolled in the access system?

Yes. That is exactly what that means.

[XEMON]

awesome, thanks

Now im wondering wither i should go for NExT on one side and xM1 on the other
Or xEM and xM1 on one side and xDF2 (or wait for the apex) on the other …

[Zwack]

Unless you have a reason for a desfire chip I would wait for Apex. It is Flex only at the moment.

[XEMON]

thanks for the input.
I do not have a use for the desfire atm, the only use i have is the T5577 and M1K …
The nfc would be to play with link and such … more and more leaning toward the xEM & xM1 duo, leaving the other hand for future use (Apex + xEM …) but the NExT is so tempting …

I dont see much implant on the inner wrist, any specific reasons for it?
any issue with wearing bracelets and watches with inner wrist implant?

[amal]

I’m considering opening up the 32k ndef applet option again on the P71 chip now that deployment seems to be working properly… so you could have, in theory, a 32kB ndef container on an Apex… but more testing is necessary.

[Pilgrimsmaster]

@XEMON

more and more leaning toward the xEM & xM1 duo

Currently in my L0 I have a Spark 1 in my R0 I have a NExT

Soon™ I will relocate my Spark 1, and I will be putting an xM1 and xEM into my L0

FOR ME, this will be an ideal setup, Across both hands in my Position 0’s it gives me
2 x LF emulators ( I can run 2 different modes and they are easily changeable )
Multipurpose HF ( NTAG216 )
Changeable NUID (Mifare “Magic” 1k)

In my opinion, the xEM and xM1 are a viable and very usable option, now you just need to decide on your other implants.
If it was me

NOW:
xM1 + xEM
NExT

IMMINENT ™ , but no so imminent you should wait to place your first order

Apex…

Remember you have other places you can put your implants

Naming convention for implant locations in the hand

During a discussion on another thread in this forum, it became clear that a naming convention of some sort should be made for the implant locations in the hand. I simply modeled the way dentists talk about teeth in the mouth, and concluded the following should suffice. Multiple chips in one hand Before I get into possible implant locations, I want to first address the idea of implanting multiple chips in the same hand or in close proximity. There a few primary considerations; Keep at least …

Implant Sutra - An index of implant positions that have been discussed and/or tried

In short This post as all about location, location, location! While planning my current batch of implants it became apparent there is LOTS of great information on this forum about implant locations but the number of threads and opinions is a tad overwhelming. This is especially for newbies and results in multiple “Implant location plan” thread’s. With this in mind I have tried to recall all the implant locations I have seen discussed or showcased on this forum to list them and any …

[XEMON]

@amal

I’m considering opening up the 32k ndef applet option again on the P71 chip now that deployment seems to be working properly… so you could have, in theory, a 32kB ndef container on an Apex… but more testing is necessary.

That’s awesome, this is only for the NFC Type4 section of the Apex right?
I thought the Apex had about 300kb for the applets …

@Pilgrimsmaster

Soon™ I will relocate my Spark 1, and I will be putting an xM1 and xEM into my L0

Thats the combo and location im thinking … leaves room for whatever cool is gonna happen on L0 (and can always add an xEM there to complete the set …)

[amal]

@XEMON

That’s awesome, this is only for the NFC Type4 section of the Apex right?

The NDEF applet creates a type 4 container on Apex, addressable using the standard NFC type 4 AID.

@XEMON

I thought the Apex had about 300kb for the applets …

Actually that needs to be updated … the true available space for applets and user data is about 80kB.

[XEMON]

This thread helped understand a bit better the Apex/NDEF: NDEF size of the Vivokey Apex line

@amal

the size of the NDEF container is what matters… so on the DESFire EV2 chip, which has 8k, you can define an NDEF container that is 1k, 2k, 3.878317k, 5.89k or all 8k… if you do that, then you can write up to 8k of NDEF data into the container that is formatted into one or more NDEF messages, each of which can have one or more NDEF records. Typically there is only ever one NDEF message, and inside that there are one or more records… so in NFC Tools when you want to write multiple things to your tag, you are creating multiple records within the single NDEF message on the chip… it just happens that on the DESFire that NDEF data is stored inside of an application ID that is defined as a generic binary data storage “file” (applications are called files on DESFire chips) with a specific AID of D2760000850100… on the Apex, the AID D2760000850100 will be a special javacard applet that also supports generic memory read/write commands for storing NDEF formatted data… and the size of that container on the Apex can, in theory, be up to 300k or more… but because of the limitations of data storage and throughput practicalities, we have limited the maximum size of the NDEF container to 16k for the NDEF applet on Apex. We did have a 32k size at one time, but it caused actual problems because it took so very long to provision NDEF data storage within the applet that phones and readers were basically timing out the NFC command and giving up.

Thanks

[XEMON]

Still trying to figure out which implant to got where (I’m probably gonna pull the trigger by the end of the month …)

So far I’m thinking xM1 and xEM in L0 for work access, but I’m starting to play with home access and having a fixed UID is becoming important.
So I’m looking at the xSIID …

Had anyone ever used one on the top of the wrist/above the watch?
Any pro/con to know?

Otherwise I’m returning to the NExT and finding another stop for the xM1 …

[Compgeek]

xEM and xM1 in L0 and NExT in R0 is also my current installation, can confirm its pretty great if your readers are good enough to couple well with glassies. xMT in R-WATCH (?) position rounds out the set for me on the applications that needed further range.

Possible ones I’m considering for next steps are Apex and maybe flexClass in L3 and R3 positions.

Personally I’m not the biggest fan of the idea of a glass bump in my wrist, more a fan of flex implants there. I also avoided my left wrist since I didn’t want any trouble with my Apple Watch NFC.

[Pilgrimsmaster]

Yeah, that sounds like a well thought out and usable setup. Thanks for the heads up om the xM1 & xEM positioning.

we will be Twinsies

xEM and xM1 in L0 and NExT in R0

I will splint between the 2 and tape them down whilst they encapsulate…

[XEMON]

We will!
I just got my order #
Got the “ultimate” bundle and added an xEM and a HF x field detector to have 2 full sets.
Probably not gonna install the spark (I’m not installing something I don’t have full understanding of what it does…)

How long do you need to keep them splinted?
I was thinking side by side, along the metacarpal of each fingers.

[Pilgrimsmaster]

@XEMON

How long do you need to keep them splinted?

This depends on your own body and the collagen production, if you are taking prenatals etc.

@XEMON

I was thinking side by side, along the metacarpal of each fingers.

Depending on where exactly you are thinking of, you may not need to splint between them.

Naming convention for implant locations in the hand

During a discussion on another thread in this forum, it became clear that a naming convention of some sort should be made for the implant locations in the hand. I simply modeled the way dentists talk about teeth in the mouth, and concluded the following should suffice. Multiple chips in one hand Before I get into possible implant locations, I want to first address the idea of implanting multiple chips in the same hand or in close proximity. There a few primary considerations; Keep at least …

[XEMON]

I was thinking L0 for the 2, one toward the index, the other towards the thumb.

But maybe that’s not the proper way to get at it

[enginerd]

Some people do just that, in fact, I’m planning to get an xDF2 and an xEM installed in L0. But do keep any chips that run at the same frequency separate, this doesn’t apply to the xLED Field Detector as it’s just a light with no chip.

Also, there’s a X-ray thread and it contains examples of people with two chips in position 0:

@Satakjar

[XEMON]

Perfect, thanks for the confirmation.
The pla:

• L0: xEM & xM1
• R0: NExT

The spark may (probably) not get installed … I dont have a case use for it (yet?)

[XEMON]

Ok, got my shipment today

But that brought up some wired questions …
I can’t read through all the packaging and the needle (as expected), should I try to read before injection to confirm proper operation?

Also, are the needle lubricated?

As a side note, is there any other applications of the Spark2 than the 2FA through vivokey?
Basically, what can I do with it?
I want to know what I can do with it before deciding to inject it or open the packaging and use the implant for testing …

[Pilgrimsmaster]

@XEMON

should I try to read before injection to confirm proper operation?

Nope…Just trust that it will work.
We all did, The chance of getting a failure is extremely unlikely.
There are quite a number of threads and posts by people thinking that their implants are not working, but most, if not all are “operator error”, but you have been around long enough to know this.

@XEMON

Also, are the needle lubricated?

Yeah they are, lightly, I havent had an issue with penetration, but more lube would make it even easier ( I have never used additional lube for an xSeries )

@XEMON

is there any other applications of the Spark2 than the 2FA through vivokey?

Are you planning on getting an Apex? If so, your Spark will act as a backup to your account.

So you are aware of using your account for logging in to the forum and Vivokey Forum, also if you have a wordpress site, you can do the same etc.
The Spark will also provide you another means of sharing contact info or url links.

Also this brilliant piece of work bu @pips

Expanding VivoKey Spark's usage to the broader web

Hi all, I am working on connecting VivoKey Connect (the OIDC platform for the Spark) to allow me to use my VivoKey Spark to sign in to my standard accounts; gmail, youtube, etc. I posted a thread in the Vivokey community, but I thought I might cross post here as well, if that’s okay. (feel free to delete this post if that’s not allowed.) My current goal is to target the “Sign In with Google” option that is present with most websites, and make it redirect authentication to VivoKey Connect. In m…

Heres the official webpage info

Expanding VivoKey Spark's usage to the broader web

Hi all, I am working on connecting VivoKey Connect (the OIDC platform for the Spark) to allow me to use my VivoKey Spark to sign in to my standard accounts; gmail, youtube, etc. I posted a thread in the Vivokey community, but I thought I might cross post here as well, if that’s okay. (feel free to delete this post if that’s not allowed.) My current goal is to target the “Sign In with Google” option that is present with most websites, and make it redirect authentication to VivoKey Connect. In m…

I expect, but cant gurantee, that when Apex is released, there may be a couple of functionalities that may trickle over.

I hope that answers your questions

Fire away if you have more

[yeka]

@Pilgrimsmaster

I expect, but cant gurantee, that when Apex is released, there may be a couple of functionalities that may trickle over.

Surely will. Much stuff can be done with Sparks theoretically and VK promised to do what works, just that the login is different on Apex, tech wise.

At least everything that just requires a VK login will easily work with Sparks.

That said, much other stuff just can’t be done on Sparks, so it will always be very limited compared to Apexes.