Consensys / orchestrate

Orchestrate is a blockchain Transaction Orchestration system that can operate multiple chains simultaneously

Consensys/orchestrate Issues

tx-sender falil and restart container - 08100@broker.sarama: 24000@: 24000@: job status was updated since user request was sent\n\n"
Updated 10 months ago
Nonce incremented when retrying a transaction due to gas price policy
Updated 2 years ago
Compatibility with Redis Cluster and Redis Sentinel
Updated 2 years ago
Store network type in chain registry (tessera, orion,....)
Updated 2 years ago
Sentry max retries as ENV var
Updated 2 years ago
Sentry max retries as ENV var
Updated 2 years ago
https://github.com/ConsenSys/orchestrate-priv/issues/939
Updated 2 years ago
Fix code scanning alert - Clear-text logging of sensitive information
Updated 2 years ago
Fix code scanning alert - Log entries created from user input
Updated 2 years ago
Faucet cooldown does not work in HA setups
Updated 2 years ago
Change Revert Reason implementation to be cross client compatible
Updated 2 years ago
Implement chain soft delete
Updated 2 years ago
Update Nonce Manager flow
Updated 2 years ago
Improve Jobs state machine with a State pattern
Updated 2 years ago
Implement HA cache compatible solution
Updated 2 years ago
Return basic data from external transactions
Updated 2 years ago
Magic numbers
Updated 2 years ago
Store proxy-cache in Redis
Updated 2 years ago