-
Currently, in the Aptos contracts, [`complete_transfer`](https://github.com/wormhole-foundation/wormhole/blob/9824d71fe1885f20eee368eac7609d0b47abb983/aptos/token_bridge/sources/complete_transfer.move…
-
**Describe the bug**
Abstract Test 136 expects 400 in the response but the OGC EDR specification states under /conf/locations/no-query-params:
Validate that a GeoJSON document was returned with a st…
-
a new endpoint should be created to support showing relayer data the same way it is currently used from the relayer status api.
```
/api/v1/relays/{chain_id}/{emitter}/{seq}
```
This will return the…
gipsh updated
11 months ago
-
We are currently filtering by transaction `to` address and then by the method invoked, when we could be doing it through getting the logs for the `TransferRedeemed` event (topic `0xcaf280c8cfeba144da6…
-
There are vaa emitted by this contract `000000000000000000000000ba7bac71a8ee550d89b827fe6d67bc3dca07b104` in some evm chains like bsc, optimism, eth, and others.
They seem to be transfers but we d…
-
Message source so we can filter
{ "source": "event-watcher", type: "create", "message_jd": "", "fields": { "vaa": { -- } -- -- -- -- -- } }
Adding the messages a source field, we can send every…
-
Create a service that observe the logs of all core layer contracts in all wormhole supported blockchains,
persiste the data (txHash, vaa and payload) and notify the event into a queue
```[tasklist]…
-
# Description
I recognized that files once scanned are not re-scanned on update or change by (remote) clients.
This open a door to distribute corrupted files marked as `clean` and is not the expe…
-
As a user i want to see the details of a transaction when its destination is osmosis.
When a VAA is destined to wormchain (chainID: 3104) like [this](https://api.testnet.wormscan.io/api/v1/transactio…
-
using paramiko 2.4.2 with python 2.7.9
cffi==1.12.2
bcrypt==3.1.6
cryptography==2.6.1
on Centos 6.9
Unable to run paramiko although libffi is installed:
```
File "/home/vaasdev/vaasdev_re…