ethereum-bloom-filters
Advanced tools
Comparing version 1.0.7 to 1.0.8
{ | ||
"name": "ethereum-bloom-filters", | ||
"version": "1.0.7", | ||
"version": "1.0.8", | ||
"description": "Ability to test bloom filters for ethereum.", | ||
@@ -5,0 +5,0 @@ "main": "dist/index.js", |
@@ -47,3 +47,3 @@ [![npm version](https://badge.fury.io/js/ethereum-bloom-filters.svg)](https://badge.fury.io/js/ethereum-bloom-filters) | ||
isTopicInBloom, | ||
isInBloom | ||
isInBloom, | ||
} from 'ethereum-bloom-filters'; | ||
@@ -87,2 +87,6 @@ ``` | ||
## Requirements for blooms to be queryable | ||
Blooms do not work with eth transactions (purely sending eth), eth transactions do not emit logs so do not exist in the bloom filter. This is what ethereum did purposely but it means you should query the eth balance every block to make sure it's in sync. Blooms will only work if the transaction emits an event which then ends up in the logs. The bloom filter is there to help you find logs. A contract can be written which does not emit an event and in that case, would not be queryable from a bloom filter. The erc20 token spec requires you to fire an event on `approval` and `transfer` so blooms will work for `approval` and `transfer` for ALL erc20 tokens, this will be most people's primary use-case. Saying that this can be used in any way you want with any use-case as long as events are emitted you it's queryable. | ||
## Functions | ||
@@ -89,0 +93,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
19036
177