TooManyFieldsInIdentityInfo
Error v151 → current 17.1Your identity registration includes more additional fields than allowed.
Why This Error Exists
Identity storage has limits to prevent abuse and keep the chain efficient. The MaxAdditionalFields constant caps how many custom fields you can add beyond the standard set (display, email, web, etc.). This error means you exceeded that limit.
Deep Dive
Standard identity fields (display, legal, web, riot, email, twitter, image) don't count toward this limit - only additional custom fields do. The limit is typically quite small (often 1-2 fields) to keep identities focused and storage-efficient.
Debugging Example
MaxAdditionalFields is 1. You try to register with additional fields: 'discord' and 'telegram'. Error: TooManyFieldsInIdentityInfo. You have 2 additional fields but limit is 1. Solution: Remove one custom field. Keep only 'discord' OR 'telegram', not both.
Prevention Tips
- Query Registry.MaxAdditionalFields before building identity info
- Prioritize which custom fields are most important
- Use standard fields where possible - they're 'free' (don't count toward limit)
From Chain Metadata
Account passed too many additional fields to their identity
What This Means
Your identity registration includes more additional fields than allowed.
Common Causes
- Number of additional fields exceeds MaxAdditionalFields constant
- Trying to register too much custom information
- Not accounting for the field limit when building identity info
How to Fix
- Check Registry.MaxAdditionalFields constant for the limit
- Reduce the number of additional (custom) fields in your identity
- Keep only essential custom fields; use standard fields where possible
Storage to Check
Runtime Info
- Pallet Index
- 17
- Error Index
- 1
- Error Code
- 17.1
- Runtime Version
- v393