7c6e4c597c
node: Fix issue where transfers that were loaded from the DB did not add a flow-cancel transfer on the TargetChain Flow-canceling is done in the `ProcessMsgForTime` loop when a new message occurs. However, this was not done when a node restarted and reloaded transfers from the past 24 hours. As a result it was possible for the node to calculate a result that showed that the outgoing transfers for an emitter chain exceeded the daily limit. In effect this is true but only with the condition that there was incoming flow to allow this to happen. This appeared to violate an invariant and so the node did not start properly. Add unit tests when reloading flow cancel transactions from the database |
||
|---|---|---|
| .github | ||
| .run | ||
| algorand | ||
| aptos | ||
| clients | ||
| cosmwasm | ||
| dashboards | ||
| deployments | ||
| devnet | ||
| docs | ||
| ethereum | ||
| lp_ui | ||
| near | ||
| node | ||
| proto | ||
| relayer | ||
| scripts | ||
| sdk | ||
| solana | ||
| spydk/js | ||
| sui | ||
| terra | ||
| testing | ||
| third_party | ||
| tilt_modules | ||
| tools | ||
| whitepapers | ||
| wormchain | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| .nvmrc | ||
| .prettierignore | ||
| .spr.yml | ||
| CONTRIBUTING.md | ||
| DEVELOP.md | ||
| Dockerfile.cli | ||
| Dockerfile.const | ||
| Dockerfile.proto | ||
| LICENSE | ||
| Makefile | ||
| Makefile.help | ||
| README.md | ||
| SECURITY.md | ||
| Tiltfile | ||
| buf.gen.web.yaml | ||
| buf.gen.yaml | ||
| buf.lock | ||
| buf.yaml | ||
| cspell-custom-words.txt | ||
| cspell.config.yaml | ||
| generate-abi-celo.sh | ||
| generate-abi.sh | ||
| package-lock.json | ||
README.md
This monorepo contains the reference implementation of the Wormhole protocol.
To learn about how to use and build on Wormhole read the docs.
See Live Contracts for current testnet and mainnet deployments of the Wormhole smart contracts.
See DEVELOP.md for instructions on how to set up a local devnet, CONTRIBUTING.md for instructions on how to contribute to this project, and SECURITY.md for more information about our security audits and bug bounty program.
See docs/operations.md for node operator instructions.
⚠ This software is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Or plainly spoken - this is a very complex piece of software which targets a bleeding-edge, experimental smart contract runtime. Mistakes happen, and no matter how hard you try and whether you pay someone to audit it, it may eat your tokens, set your printer on fire or startle your cat. Cryptocurrencies are a high-risk investment, no matter how fancy.