refactor: update import paths and API calls for OZ v0.6.0 module structure

[aguilar1x]

Context

Depends on #2 (dependency migration). Once Cargo.toml is updated the Rust source will fail to compile because the module paths and public API changed significantly between v0.3.0 and v0.6.0.

Import path changes

Old (v0.3.0)	New (v0.6.0)
use stellar_fungible::Base;	use stellar_tokens::fungible::{Base, FungibleToken};
use stellar_access_control as access_control;	use stellar_access::access_control;
use stellar_pausable as pausable;	use stellar_contract_utils::pausable;
use stellar_pausable_macros::when_not_paused;	use stellar_macros::when_not_paused;
use stellar_upgradeable_macros::...;	use stellar_macros::...;

API call changes

Access control

// v0.3.0
access_control::ensure_role(&env, &caller, &Symbol::new(&env, MINTER_ROLE));
access_control::has_role(&env, &address, &role_symbol).is_some()
access_control::get_admin(&env)

// v0.6.0
access_control::ensure_role(&env, &caller, &Symbol::new(&env, MINTER_ROLE)); // same
access_control::has_role(&env, &address, &role_symbol)  // returns Option<u32>
access_control::get_admin(&env)  // same

Pausable

// v0.3.0
pausable::paused(&env)
pausable::pause(&env)
pausable::unpause(&env)

// v0.6.0  — same function signatures, different module path
stellar_contract_utils::pausable::paused(&env)
stellar_contract_utils::pausable::pause(&env)
stellar_contract_utils::pausable::unpause(&env)

Fungible Base

// v0.3.0
Base::mint(&env, &to, amount)
Base::transfer(&env, &from, &to, amount)   // to: &Address
Base::burn(&env, &from, amount)

// v0.6.0
Base::mint(&env, &to, amount)              // same
Base::transfer(&env, &from, &to, amount)   // to: &MuxedAddress  ← breaking change
Base::burn(&env, &from, amount)            // same

Files to update

• Contracts/stablecoin/src/contract.rs — all use/import statements + transfer / transfer_from signatures
• Contracts/stablecoin/src/extensions/burnable.rs
• Contracts/stablecoin/src/extensions/pausable.rs
• Contracts/stablecoin/src/extensions/upgradeable.rs
• Contracts/stablecoin/src/utils.rs

Acceptance criteria

• All use statements reference the new v0.6.0 module paths
• transfer and transfer_from accept MuxedAddress for the to parameter
• cargo build compiles without errors

[Anuoluwapo25]

Hi maintainer, I'd like to take on this issue as i'll fully implement what is requested as i'm a fullstack web3 developer with experiences.

[ReinaMaze]

Gm, I’d like to work on this issue.
I have experience contributing to open source issues.
I’ve reviewed the description and understand what needs to be done.
Kindly assign this issue to me

[Otaiki1]

I have experience building blockchain applications , let me work on this
Will submit a working PR in 24 hours after assignment

[aguilar1x]

For this issue you need to wait until issue #2 is finished

@Anuoluwapo25

[Anuoluwapo25]

For this issue you need to wait until issue #2 is finished

@Anuoluwapo25

Alright, thank you.

[aguilar1x]

you can start the issue now!

@Anuoluwapo25

[Anuoluwapo25]

Okay

…

On Tue, Mar 10, 2026 at 5:13 AM Matias Aguilar ***@***.***> wrote: *aguilar1x* left a comment (PACTO-LAT/stablecoin#3) <#3 (comment)> you can start the issue now! @Anuoluwapo25 <https://github.com/Anuoluwapo25> — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A55OV7TV6ASDKC6PGEU6YLD4P6I43AVCNFSM6AAAAACV6YW7JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMRYGUZTKNRQGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>