Skip to content

[Feature]: Request: Add Blocks (B) SIP-010 token to Stacks crypto-assets-service #17296

@mrwagmibtc

Description

@mrwagmibtc

Library name

No response

Describe your feature request

Summary

Requesting addition of the Blocks (B) SIP-010 fungible token to Ledger's
Stacks token support, following the framework merged in #12168 and
LedgerHQ/crypto-icons#70.

This issue is to request the token be added to the crypto-assets-service
backend (CAL). I'm prepared to open a companion icon PR to
LedgerHQ/crypto-icons once the backend entry exists, since the verification
script there checks IDs against the service.

cc @emmanuelm41 @lawRathod @gre-ledger @semeano — apologies for the direct
ping; the public-facing token submission form covers EVM chains only and
Ledger Support directed me to GitHub for SIP-10 requests.

Token Information

Project Links

Verification Links

Liquidity Venues

Proposed Ledger ID

Following the convention used in LedgerHQ/crypto-icons#70: stacks/sip010/blocks_spv9k21tbfak4knrjxf5dfp8n7w46g4v9rcjdc22.b-faktory::B

(Open to whatever ID format the crypto-assets-service prefers.)

About the Token

Blocks is a community memecoin and digital collectible on Stacks. The metadata explicitly discloses memecoin status with no utility or promised returns, in line with similar already-listed tokens (WELSH, MEGA, ROO, NOT, SKULL).

Asset Files

I have a 144×144 PNG icon prepared per the crypto-icons repo guidelines
(opaque background, ~15KB) ready to submit via PR once this entry is added.

Happy to provide additional info — volume figures, holder count, etc. — on request.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    librariesImpacts the LibrariestriageIn need of triage

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions