In the current SEDIMARK onboarding scenario we rely on this component for supporting IOTA identity framework, but we also depend on external tools (i.e. Metamask wallet) to support Ethereum Smart Contract operations.
As IOTA SDK seems to support wallet generation, why not to unify both identities and store them on the IOTA stronghold vault? Personally, I'd rather prefer to transition to a single dependency for offloading crypto/DLT related operations.
Should we identify the chainid on the EOA blockchainAccountId DID part according to https://chainagnostic.org/CAIPs/caip-10? (so replace the eip155:1: prefix by something else).
In the current SEDIMARK onboarding scenario we rely on this component for supporting IOTA identity framework, but we also depend on external tools (i.e. Metamask wallet) to support Ethereum Smart Contract operations.
As IOTA SDK seems to support wallet generation, why not to unify both identities and store them on the IOTA stronghold vault? Personally, I'd rather prefer to transition to a single dependency for offloading crypto/DLT related operations.