What problem does it solve?
Managing raw private keys in application code is a security risk. This Skill shows how to sign Ethereum transactions using keys generated and stored inside cloud HSMs (AWS KMS or Azure Key Vault), so private keys are never exported or exposed in your .NET application.
Core Features & Use Cases
- AWS KMS Signing: Create secp256k1 keys in AWS KMS and sign Ethereum transactions via
Nethereum.Signer.AWSKeyManagement with default, explicit, or region-specific credentials.
- Azure Key Vault Signing: Create SECP256K1 keys in Azure Key Vault and sign via
Nethereum.Signer.AzureKeyVault using DefaultAzureCredential, managed identity, or service principal authentication.
- Full Transaction Support: Both signers support Legacy, EIP-1559, EIP-2930, and EIP-7702 transaction types through Nethereum's
ExternalAccount.
- Use Case: A serverless backend (AWS Lambda or Azure Function) needs to send ETH or interact with smart contracts without storing a private key file. Use this Skill to wire a cloud HSM key into a Nethereum
Web3 instance and broadcast signed transactions.
Quick Start
Show me how to sign and send an Ethereum transaction in C# using an AWS KMS key with Nethereum.