How to add your contracts’ function and event signatures into Boost’s well-known registry
@boostxyz/signatures
in the creation of your Boost, then you don’t have to do anything else for validation to work.
Otherwise, if you’re supplying a custom event signature unknown to @boostxyz/signatures
and dealing with a Boost using a custom validator, you’ll need to additionally supply your own AbiEvent
to validation methods so event logs can be correctly pulled off transactions.
@boostxyz/signatures
is preferred due to its approach as a static manifest as opposed to a third party API.@boostxyz/signatures
already supports your signature. We include several popular signatures and you may not need to do anything at all.boostxyz/boost-protocol
repository//
are treated as comments so you can distinguish a block of related signatures@boostxyz/signatures
package so you can continue your Boost Protocol integrations.