Use runes-compatible token symbol

[whoabuddy]

Runes tickers for each dao will be formatted based on their token names:
FACES•AIBTC•DAO

For SIP-010 tokens we cannot use the same symbol, so we will use - instead e.g.
FACES-AIBTC-DAO

We need to create this as the symbol in the token contract based on the token name.

We also need to display this correctly in the frontend (separate issue).

[whoabuddy]

Thinking this through @Rapha-btc we can collab on this one to simplify our process a bit. Reiterating below for the full picture.

---

Right now our scripts to generate a DAO accept a symbol and name for the SIP-010 token, and we pass that to the generator.

• usage example for generate-dao

We can reduce the input to just the symbol since that's what we build everything off of. No need to specify a separate name.

The rune gets etched with the fancy format:

• FACES•AIBTC•DAO
• FAK•AIBTC•DAO
• FUN•AIBTC•DAO

Then we create the SIP-010 with both symbol and name set to the equivalent:

• FACES-AIBTC-DAO
• FAK-AIBTC-DAO
• FUN-AIBTC-DAO

And on the frontend have a formatting function to turn the - into • for any dao token symbol/name.

Open to some push-back here if we think symbol should just be the symbol and name is the full -AIBTC-DAO variant. Initial thinking is having them the same means it will always show correctly in any interface e.g. Hiro Explorer, stxtools.io, fakory.fun, etc.

[Rapha-btc]

Yes. Having the SIP-10 symbol match the rune's ticker aligns tokens.

For example,

• Rune Ticker: FACES•AIBTC•DAO
• SIP-10 asset symbol: (define-fungible-token FACES-AIBTC-DAO MAX)

Can the SIP-10's name be set back to FACES•AIBTC•DAO?

Can the SIP-10 include the Rune's symbol, a 1 char that can be an emoji.
For example,

• (define-constant TOKEN-RUNE-SYMBOL "👹") @whoabuddy

[whoabuddy]

No name/symbol cannot be set to use • because they are string-ascii type.

So for sure we want to make sure that these are consistent:

1. Rune ticker: FACES•AIBTC•DAO
2. SIP-010 asset: FACES-AIBTC-DAO
3. SIP-010 symbol: FACES-AIBTC-DAO
4. SIP-010 name: FACES-AIBTC-DAO

That way it's consistent no matter where it shows, and in our UI we can replace the symbols for better display.

As far as the symbol - we could include runes-specific items as a constant depending on what information we have after the etch / before the bridge.

• (define-constant TOKEN-RUNE-SYMBOL "👹")
• (define-constant TOKEN-RUNE-NUMBER u41345)
• anything else? any standard for this in existing SIP-010 runes like roons?