Skip to content

Commit

Permalink
Release/0.5.1 (#78)
Browse files Browse the repository at this point in the history
* release: 0.5.1

* Add release binaries for

* doc updates

* windows release

---------

Co-authored-by: github-actions <[email protected]>
  • Loading branch information
joshstevens19 and github-actions committed Aug 7, 2024
1 parent e76fefd commit d2a78f9
Show file tree
Hide file tree
Showing 13 changed files with 151 additions and 3 deletions.
16 changes: 14 additions & 2 deletions documentation/docs/pages/docs/changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@
### Bug fixes
-------------------------------------------------

- fix: resolve unhandled solidity types in solidity_type_to_ethereum_sql_type_wrapper

### Breaking changes
-------------------------------------------------

Expand All @@ -19,6 +17,20 @@

all release branches are deployed through `release/VERSION_NUMBER` branches

## 0.5.1-beta - 7th August 2024

github branch - https://github.com/joshstevens19/rindexer/tree/release/0.5.1

- linux binary - https://rindexer.xyz/releases/linux-amd64/0.5.1/rindexer_linux-amd64.tar.gz
- mac apple silicon binary - https://rindexer.xyz/releases/darwin-arm64/0.5.1/rindexer_darwin-arm64.tar.gz
- mac apple intel binary - https://rindexer.xyz/releases/darwin-amd64/0.5.1/rindexer_darwin-amd64.tar.gz
- windows binary - https://rindexer/releases.xyz/win32-amd64/0.5.1/rindexer_win32-amd64.zip

### Bug fixes
-------------------------------------------------

- fix: resolve unhandled solidity types in solidity_type_to_ethereum_sql_type_wrapper

## 0.5.0-beta - 6th August 2024

github branch - https://github.com/joshstevens19/rindexer/tree/release/0.5.0
Expand Down
35 changes: 35 additions & 0 deletions documentation/docs/pages/docs/start-building/streams/kafka.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,41 @@ contracts:
:::
## Response
:::info
Note SNS/SQS may wrap the message body into their own object so the below is just what we send to the stream.
:::
The response sent to you is already decoded and parsed into a JSON object.
- `event_name` - The name of the event
- `event_data` - The event data which has all the event fields decoded and the transaction information which is under `transaction_information`
- `network` - The network the event was emitted on

For example a transfer event would look like:

```json
{
"event_name": "Transfer",
"event_data": {
"from": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"to": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"value": "1000000000000000000",
"transaction_information": {
"address": "0xae78736cd615f374d3085123a210448e74fc6393",
"block_hash": "0x8461da7a1d4b47190a01fa6eae219be40aacffab0dd64af7259b2d404572c3d9",
"block_number": "18718011",
"log_index": "0",
"network": "ethereum",
"transaction_hash": "0x145c6705ffbf461e85d08b4a7f5850d6b52a7364d93a057722ca1194034f3ba4",
"transaction_index": "0"
}
},
"network": "ethereum"
}
```

## brokers

You define the kafka brokers you wish to connect to, you can pass in multiple brokers if you wish. A single broker
Expand Down
35 changes: 35 additions & 0 deletions documentation/docs/pages/docs/start-building/streams/rabbitmq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,41 @@ contracts:
:::
## Response
:::info
Note SNS/SQS may wrap the message body into their own object so the below is just what we send to the stream.
:::
The response sent to you is already decoded and parsed into a JSON object.
- `event_name` - The name of the event
- `event_data` - The event data which has all the event fields decoded and the transaction information which is under `transaction_information`
- `network` - The network the event was emitted on

For example a transfer event would look like:

```json
{
"event_name": "Transfer",
"event_data": {
"from": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"to": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"value": "1000000000000000000",
"transaction_information": {
"address": "0xae78736cd615f374d3085123a210448e74fc6393",
"block_hash": "0x8461da7a1d4b47190a01fa6eae219be40aacffab0dd64af7259b2d404572c3d9",
"block_number": "18718011",
"log_index": "0",
"network": "ethereum",
"transaction_hash": "0x145c6705ffbf461e85d08b4a7f5850d6b52a7364d93a057722ca1194034f3ba4",
"transaction_index": "0"
}
},
"network": "ethereum"
}
```

## url

This is the rabbitmq connection url we advise to put this in a environment variable.
Expand Down
35 changes: 35 additions & 0 deletions documentation/docs/pages/docs/start-building/streams/sns.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,41 @@ contracts:
- event_name: Transfer // [!code focus]
```
## Response
:::info
Note SNS/SQS may wrap the message body into their own object so the below is just what we send to the stream.
:::
The response sent to you is already decoded and parsed into a JSON stringify object.
- `event_name` - The name of the event
- `event_data` - The event data which has all the event fields decoded and the transaction information which is under `transaction_information`
- `network` - The network the event was emitted on

For example a transfer event would look like:

```json
{
"event_name": "Transfer",
"event_data": {
"from": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"to": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"value": "1000000000000000000",
"transaction_information": {
"address": "0xae78736cd615f374d3085123a210448e74fc6393",
"block_hash": "0x8461da7a1d4b47190a01fa6eae219be40aacffab0dd64af7259b2d404572c3d9",
"block_number": "18718011",
"log_index": "0",
"network": "ethereum",
"transaction_hash": "0x145c6705ffbf461e85d08b4a7f5850d6b52a7364d93a057722ca1194034f3ba4",
"transaction_index": "0"
}
},
"network": "ethereum"
}
```

## aws_config

This is the AWS configuration for the SNS client.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,40 @@ contracts:
- event_name: Transfer // [!code focus]
```
## Response
The response sent to you is already decoded and parsed into a JSON object.
- `event_name` - The name of the event
- `event_data` - The event data which has all the event fields decoded and the transaction information which is under `transaction_information`
- `network` - The network the event was emitted on

For example a transfer event would look like:

```json
{
"event_name": "Transfer",
"event_data": {
"from": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"to": "0x0338ce5020c447f7e668dc2ef778025ce3982662",
"value": "1000000000000000000",
"transaction_information": {
"address": "0xae78736cd615f374d3085123a210448e74fc6393",
"block_hash": "0x8461da7a1d4b47190a01fa6eae219be40aacffab0dd64af7259b2d404572c3d9",
"block_number": "18718011",
"log_index": "0",
"network": "ethereum",
"transaction_hash": "0x145c6705ffbf461e85d08b4a7f5850d6b52a7364d93a057722ca1194034f3ba4",
"transaction_index": "0"
}
},
"network": "ethereum"
}
```

## endpoint

This is your rabbitmq url.
This is your webhook url.

```yaml [rindexer.yaml]
...
Expand Down
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 comments on commit d2a78f9

Please sign in to comment.