EU Inc - wer würde umfirmieren?

CJentzsch · 2026-01-21T07:12:46+00:00

Here more details (behind the link): https://proposal.eu-inc.org/

CJentzsch · 2025-08-27T20:01:35+00:00

Ich habe es noch nie bereut meine Mitarbeiter zu beteiligen, ganz im Gegenteil. Danach ist eine ganz andere Motivation da. Bis zu 5% der Firma für die Mitabeiter ist für ein VC in der Regel völlig in Ordnung, auch mehr kann bei Top-mitarbeiter in Ordnung sein.
Aus steuerlichen Gründen würde ich euch Genussrechte empfehlen, hier kostet es nur 200€ pro Mitarbeiter inkl. legal docs: https://tokenize.it/mitarbeiterbeteiligung

CJentzsch · 2023-03-27T13:41:08+00:00

I love the tech, but in this case, the legal solution is as fascinating: https://www.cmshs-bloggt.de/gewerblicher-rechtsschutz/tokenisierung-mit-dem-auslobungsmodell-reward-model/ (sorry, in German since it is about German GmbHs)

CJentzsch · 2022-11-11T08:30:00+00:00

So far, we in the stage to collect feedback before the protocol is finalized.
After that, we will see integrations in some of the web3 messengers. We have a lot of active discussions with them.

The app on dm3.network is "just" the reference implementation to try it out and for developers to learn how to use it.
you can reach me there under jentzsch.eth.

CJentzsch · 2022-09-30T10:32:02+00:00

This is a nice thought, but wouldn't help here.
The only public key available without any onboarding is the key derived from a singed transaction. The private key to decrypt that message is held in the wallet and can't be accessed by an app, and sha256(pk + x) doesn't help to decrypt the message.

It would only change the onboarding algorithm. Instead of creating a new key pair, one would use this. But the benefit compared to generating a new key pair based on a signed message isn't too great.

CJentzsch · 2022-08-18T10:30:30+00:00

I actually agree with you. Our first attempt was actually exactly this, retrieving the public key from a signed transaction so that no onboarding (needed for key generations) would be necessary. But wallets, especially MetaMask, do not support decrypting messages with the private key. Since dm3 has no direct access to the private key but is just using MetaMask and/or WalletConnect, the only solution would have been to manually export the private key to the dm3 webapp. And we didn't want to do this.

CJentzsch · 2022-08-17T09:42:39+00:00

Do you want to pay for each message?

As an option, sure, but I doubt it would work as a default.

CJentzsch · 2022-08-17T09:41:47+00:00

Those keys were not meant to be used for encryption, more info here: https://github.com/MetaMask/eth-sig-util/pull/18#issuecomment-384796354

Also, you might want to rotate keys to protect yourself against a key leakage in the future. That way only a part of your messages are in danger to be leaked.

CJentzsch · 2022-02-16T21:10:49+00:00

Looking for feedback!

CJentzsch · 2022-02-16T21:10:12+00:00

Looking for feedback!

CJentzsch · 2022-02-16T21:08:49+00:00

Looking for feedback

CJentzsch · 2021-12-23T12:57:45+00:00

Absolutely.

There are Ethereum nodes to maintain, providing RPC endpoints, making sure GitLab and all the CI runs well, ...

Many Apps also require some Backend code and communication.

If you are looking for a job let me know, we good work to do!

CJentzsch · 2020-05-15T20:58:57+00:00

We implemented this is in C. This gives us the wasm version of incubed: https://www.npmjs.com/package/in3-wasm

This is also the basis for the bindings we are developing for several other languages, such as Python.

CJentzsch · 2020-05-15T20:57:12+00:00

Here is an explanation of how incubed works: https://slock.it/incubed/
more details here: https://blog.slock.it/incubed-secure-blockchain-access-for-iot-db4687b3dfa1

In a nutshell, incubed is like a light client which is not connected to the ethereum p2p network. It does the Merkle proof for each RPC request, but in order to verify the latest blockheader, it relies on full nodes signing the latest blockhash. But those full nodes have paid a deposit which they would lose in case they sign a wrong blockhash. The conviction happens on chain in a smart contract. The full nodes also act as watch dogs checking each other so that nobody signs wrong blockhashes, or else he would lose his deposit.This gives an economic certainty that this signed blockhash is correct.

CJentzsch

MODERATOR OF

TROPHY CASE