Naming the contract that make Stellar Assets usable in Soroban

[magic marten]

Soroban will ship with a built-in (precompile) contract that exposes Stellar Assets as standard tokens in Soroban. What should we name this contract?

Proposal: "Stellar Asset Adapter"

In the past we used the terms "Bridged" or "Wrapped" which are technically inaccurate and somewhat confusing

[tall totem]

Stellar Asset Contract?

[coarse galleon]

combine them Stellar Asset Adapter Contract Colloquially known as The Saac 😆
I am less concerned with the name than knowing it's functionality but the name should reflect what it is also...

[tall totem]

I'm not fond of adapter for the same reason as bridged or wrapped. It suggests that there's this chasm between the token on Soroban and the Stellar Asset. A Stellar Asset is an implementation of the token interface. There's no chasm.

[drowsy mantle]

Is this functionality (and in general the token-wrapping) limited to stellar. If so the name 'stellar' may be omitted from the name?
Otherwise what @tall totem said or

• (Stellar/Classic) Asset Accessor
• Stellar Asset Interface
• Classic Asset Interface

A Stellar Asset is an implementation of the token interface.
stellar implementaion of token interface => siti

[brisk rune]

Any particular reason to leave the word "Native" out?
Native Asset Contract

But if you think that an import/export actually 'tokenizes' a classic stellar asset (another, perhaps flawed way to look at it) then maybe 'Native Asset Tokenizer Contract'? sure sounds like NAT = network address translation 😄 (private/public IP resolution) from networking

[tall totem]

Because this is for all Stellar assets, not only the Stellar native asset (XLM).

[brisk rune]

I use loosely native = classic sorry 🙂 then I would say "Classic Asset Tokenizer"