-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoSuchKeyset Error On Sequencer Nodes and Full Nodes. Anytrust chain. #2418
Comments
What I see on full nodes:
|
Note: This only occurs when using a custom BLS signature |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I get the error
NoSuchKeyset
on the sequencer node. When I have set a valid keyset (das_bls, das_bls.pub) and used the correctnodeConfig.json
as well. At first, it was happening whenever I ran a Full Node. Now it's happening on the sequencer node as well. There is a single DAS which is an archival DAS.To Reproduce
setValidKeysetPrepareTransactionRequest
and send the txn.Expected behavior
NoSuchKeyset(0x1c4b4d38f1f5396ecb0beee91f91df91dde26d647ca7ceaa63deb8a002e0616f)
Screenshots
I see the above logs on my sequencer node continuously now.
When I run a Full node this is what I get:
![Screenshot 2024-06-21 at 11 04 00 AM](https://private-user-images.githubusercontent.com/33081891/341651557-ece16470-3fb3-4ff9-8124-c145b9bdc467.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDg3NDMsIm5iZiI6MTcyNjE0ODQ0MywicGF0aCI6Ii8zMzA4MTg5MS8zNDE2NTE1NTctZWNlMTY0NzAtM2ZiMy00ZmY5LTgxMjQtYzE0NWI5YmRjNDY3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDEzNDA0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZjMWRiNThmMGYwMmY4ZDkxZDc3YmIzM2E1MTRmOTgyODZkYTAyZDQyYTdjNmY5NDZkZTlhYTNlMGZhNjhjNjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.xN8HhRWAJQyZFgjaLUXzsba8OmE_3A8NtFxVyl88-m8)
Completely different keyset hash. Using the same
nodeConfig.json
.My das-config on the
nodeConfig.json
file:The text was updated successfully, but these errors were encountered: