Architecture Behind Sila Ethereum Transactions
https://silamoney.com/2019/07/08/using-aws-lambda-sqs-with-web3/ https://silamoney.com/2019/07/08/using-aws-lambda-sqs-with-web3-2/ Major components DynamoDB to store the nonce associated with ethereum addresses authorized to send ethereum smart contract transactions Lambda functions triggered by SQS events for SilaToken issuance, redemption, and transfer messages Ethereum RPC EC2 servers running Parity Ethereum client AWS Secrets Manager to store private keys being used to sign the transactions Orchestrator as a bridge between REST API, ACH, and ethereum transactions. Orchestrator is a piece of code that handles the transaction state and reroutes them to right queue. SQS as an interface between different services like REST API, ACH, Ethereum issuance, redemption, and transfers. Transaction Lifecycle Messages for SilaToken issuance, redemption, and transfer comes in through Sila APIs. Dependent on the action (issue, redeem, and transfer), the message is sent to the relevant queue by Orchestrator, which in turn triggers the send transaction Lambda function. ...