Repository navigation
Three values a short-epoch devnet cannot accept - #29
Merged
Merged
Conversation
Found standing up the WI-080 peg-in sweep against a local devnet, where each one stopped the round trip with an error that named something else. `init` printed the oracle one-shot through TransactionInput's toString. That line exists to be copied into `oracle.tx-out-ref`, which parses TXHASH#INDEX and rejects everything else, so the next command failed with "Invalid TxOutRef format". It now prints the form it documents. `deploy-bridge` published the peg_in/peg_out withdraw hashes but not the ADDRESSES an SPO configures; hand-encoding a script hash eventually picks the wrong network, and the result is not an error but an address no PegInRequest is minted to. And `pegin-request`'s one-hour TTL is now bridge.pegin-request-ttl-seconds: a validity interval may not end past the node's era-forecast horizon, which reaches about one epoch, so on a short-epoch devnet an hour is unsubmittable — reported as TimeTranslationPastHorizon, which names a future slot and says nothing about the TTL.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found standing up the WI-080 peg-in sweep against a local devnet. Each of these stopped the round trip with an error that named something else.
initprinted the oracle one-shot throughTransactionInput's toString. That line exists to be copied intooracle.tx-out-ref, which parsesTXHASH#INDEXand rejects everything else — so the next command died withInvalid TxOutRef format. It now prints the form it documents.deploy-bridgepublished the peg_in/peg_out withdraw hashes but not the addresses an SPO is configured with (pegin_script_address/pegout_script_address). Bech32-encoding a script hash by hand eventually picks the wrong network, and the result is not an error but an address no PegInRequest is ever minted to — an empty bridge rather than a failure.pegin-request's one-hour TTL is nowbridge.pegin-request-ttl-seconds. A validity interval may not end past the node's era-forecast horizon, which reaches roughly one epoch; on a short-epoch devnet an hour is unsubmittable, reported asTimeTranslationPastHorizonnaming a future slot. Default unchanged at 3600.With these the peg-in round trip passes end to end on the compose bench (bridge deploy → 35-byte beacon deposit → PegInRequest → the TM spending the deposit on regtest).