Doma it goes like this (IMHO) (and just skip the first 5 paragraphs)
Wave came up with the SurfChip in order to provide a platform for the vision of a hardware secured durable-DRM client-side untethered content-metering enterprise. Nobody would bite. Somewhere along the line folks at HP and allegedly IBM and or Sun told Wave they needed something a bit more flexible to get the OEMs to bite on this share-revenue scheme.
So Wave did what they were told and innovated and came up with E2100 (or HP did if you do barge hook-line-and-sinker). So then Wave went peddling E2100 to chip fab outfits etc trying to get it front billing (and add-in board folks be they Haup or whomever). See, while Wave did have a chip spec and had fabbed some protos, bottom line is they had an office in Lee and a standing account with Krispy Kreme and little else.
Somewhere in here they went from a DRM/client-side metering service provider to a “platform” provider and the game changed to renting applet space and providing applet certification, loading, and billing services etc. You remember “only Wave had PROGRAMMABLE” client-side hardware security. The new mantra is “only Wave provides interoperability”. Over and over again when somebody said, gee look, somebody else is making a chip the answer was always “but is it programmable” later the catch phrase was “do they have a TAN”.
So Wave had to troll and slut about hoping somebody would build their chip. They managed to put together the two-piece-bumped-on-the-head-flip-chip with, who was it, Interpoint?, which was eventually written off as burnt inventory, but they did build a few CSP developer kits out of some of the detritus, a decent resourceful move). During this interval TCPA started ramping up (to nowhere) and then TCG came on line. Concurrent with this was the reality that ATML was staking out some of this space. Obviously their were others as well, and the brain-trust in Lee said, heck, what good are all of these things if they can’t interact. Sure, one could come up with 10 different user programs to effect the same thing, but that won’t really fly. Interoperability must occur ‘lower down’.
Wave had a full package in the E2100 days (IMO) a chip, TSS, CSP, and had incorporated compatibility with Java as part of the Finread requirement. Wave saw that their E2100 at $50 a crack or whatever was never going to fly (o.k. call it $20 or even $10, still wasn’t going to happen). Somewhere in here I believe they seized on the notion that the ATMLs and the Infineons were a bit too stuck on chips and could get to the app. So Wave focused on their CSP and making it crossplatform compatible and also providing serve that would serve for migration and stability across platforms. I believe they have competition for ALL of these services at this point, (less the off-the-shelf CSP).
The Point??
Wave WORKED ON their CSP and made their product fit the NICHE of interoperability. Did Infineon make sure their TSS would work on ATMLs chip? I personally doubt it. Others simply didn’t bother and went with a company that WORKED ON making their TSS work on anybody’s chip (NTRU). Now maybe you are right and TPM-TSS compatibility doesn’t amount to a hill of beans and TSS-CSP compatibility is somehow a huge piece of impenetrable Wave IP. If you are correct and TPM-TSS compatibility means nothing, then I get some crow.
I simply do not know enough about the tech to discern.
Regards,
Dig Space.
Market Data 
Markets 
AI
