Incorrect multihash type for event topic string
See original GitHub issueOur contract has a MultihashAdded
event that emits a Multihash type:
event MultihashAdded(
address indexed bullaManager,
address bullaClaim,
Multihash ipfsHash,
uint256 blocktime
);
and the resulting typechain output for the event is:
events: {
...
"MultihashAdded(address,address,tuple,uint256)": EventFragment;
...
}
it should be:
events: {
...
"MultihashAdded(address,address,(bytes32,uint8,uint8),uint256)": EventFragment;
...
}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
go-cid - Go Packages
A CIDv0 corresponds to a multihash of type DagProtobuf, ... Encoder) string; func (c Cid) Equals(o Cid) bool; func (c Cid) Hash() mh....
Read more >ContainerPartitionKey interface - Microsoft Learn
Indicates the kind of algorithm used for partitioning. For MultiHash, multiple partition keys (upto three maximum) are supported for container create.
Read more >Handling multiple event types in a topic using Confluent
In this tutorial, learn how to handling multiple event types using Confluent, with step-by-step instructions and examples.
Read more >ipfs-postmsg-proxy - npm
When messages are passed using window.postMessage the data that is sent is cloned using the structured clone algorithm. It allows more things to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@krzkaczor you stud 😎
Fixed.