Skip to content

Commit fd59288

Browse files
authored
Update CHALLENGE.md
1 parent 42115f4 commit fd59288

File tree

1 file changed

+3
-25
lines changed

1 file changed

+3
-25
lines changed

docs/CHALLENGE.md

Lines changed: 3 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Ethereum Data Service
22

3-
## Challenge Overview
3+
## Objective
44

5-
Please write a service which uses the Ethereum JSON-RPC API to store the following information in a local datastore for the most recent 50 blocks and provide a basic API:
5+
To write a service which uses the Ethereum JSON-RPC API to store the following information in a local datastore for the most recent 50 blocks and provide a basic API:
66

77
1. Get and store the block and all transaction hashes in the block.
88
2. Get and store all events related to each transaction in each block.
@@ -11,32 +11,10 @@ Please write a service which uses the Ethereum JSON-RPC API to store the followi
1111
- Get block by number.
1212
- Get transaction by hash.
1313

14-
### Use the following Validation Cloud endpoints for Ethereum Mainnet RPC access:
15-
14+
### Use the following endpoints for Ethereum Mainnet RPC access:
1615
- HTTP: `https://mainnet.ethereum.validationcloud.io/v1/JFt58zlN7gcQlLYnMZcOD75LpethJgD6Eq5nKOxC9F0`
1716
- WebSocket: `wss://mainnet.ethereum.validationcloud.io/v1/wss/JFt58zlN7gcQlLYnMZcOD75LpethJgD6Eq5nKOxC9F0`
1817

19-
### Additional Notes:
20-
21-
- Code should be written in Go.
22-
- RPC Methods which might be useful: `eth_blockNumber`, `eth_getBlockByNumber`, `eth_getTransactionByHash`, `eth_getLogs`.
23-
- Feel free to ask us questions as you go.
24-
- Include a Dockerfile to compile and build your application.
25-
- Containerize any dependencies (e.g. databases).
26-
- Include a README file with instructions on how to build the container(s) and run the application.
27-
28-
### Some inspiration for add-ons and discussion topics in our debrief:
29-
30-
- Thought process and code design.
31-
- Technology choices.
32-
- How would you keep the data set up to date?
33-
- How would you expose the stored data to customers in an easy-to-query API?
34-
- How would you handle security of the API?
35-
- How would you improve the performance of your approach?
36-
- How would you adapt your design to store the same data for the entire history of Ethereum Mainnet?
37-
- What would it take to deploy and monitor a service like this in production?
38-
39-
4018
## Project structure
4119

4220
```

0 commit comments

Comments
 (0)