-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Udpated env example and support retrieving transaction through rpc in…
…stead of a hard coded string[] Signed-off-by: linsyhen99 <linsyhen99@gmail.com>
- Loading branch information
1 parent
58a98d9
commit 3774014
Showing
4 changed files
with
74 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,4 @@ | ||
PROGRAM_HASH= | ||
IDL_TYPE= | ||
IDL_TYPE= | ||
TRANSACTION_HASH= | ||
RPC_URL= |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,37 @@ | ||
# event-parsing-with-ek | ||
|
||
A sample project that showcases the basic usages and integrations with EK-Parser that decodes the program's event data based on the IDL file | ||
|
||
## About | ||
|
||
- The list of program IDLs identified/indexed/curated by the SolanaFM's team is listed here in this library | ||
|
||
- https://www.npmjs.com/package/@solanafm/ek-idls-repo | ||
|
||
- If your IDL is not part of the identified IDLs list, you can still use the Parser by manually injecting your IDL file into the Parser object | ||
- To manually initialise the Parser with your own IDL file please follow the guide below | ||
|
||
## Populate the project with a .env file to get started | ||
|
||
- Sample env configuration file | ||
|
||
``` | ||
PROGRAM_HASH= | ||
INSTRUCTIONS= | ||
PARSER_TYPE=registry # "manual" | "registry" | ||
STARTING_BLOCK=245000000 | ||
RPC_URL= | ||
# Loading IDL from local file | ||
IDL_TYPE=shank # "anchor" | "shank" | "kinobi" | ||
``` | ||
|
||
--- | ||
|
||
# Initialising the Parser with a custom IDL file configuration | ||
|
||
1. Ensure that your IDL file is either generated by anchor/shank | ||
2. Create a `idl.json` file in the local directory and populate the json file with your generated IDL file | ||
3. Indicate your `PROGRAM_HASH` in the `.env` file | ||
4. Change your `PARSER_TYPE` to `manual` | ||
5. Indicate your `IDL_TYPE` field in the `.env` file |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters