<aside> 💡

To use this function, you must use GlueERC20 or GlueERC721 contract of a specific Sticky Token. To better understand the Glue Ecosystem architecture and find the correct deployment addresses, visit visit Lore and Architecture | License & Deployments

</aside>

The unglue function allows users to burn their sticky tokens and withdraw a proportional amount of the collateral held in the Glue contract.

• Calldata
• Return
• Usage Examples
• Event

🔥🔥 Batch Unglue

<aside> 💡

This function is from the GlueStickERC20 or the GlueStickERC721. To better understand the Glue Ecosystem architecture and find the correct deployment addresses, visit Lore and Architecture | License & Deployments

</aside>

The batchUnglue function allows users to burn multiple sticky tokens and withdraw a proportional amount of collaterals held in multiple Glue contracts.

• Calldata
• Usage Examples
• Event

Hooks

You can customize your Sticky Asset's behavior in its own Glue during the unglue operation using hooks. To learn more, visit Hooks and Expansions Pack

Self-Learning

The internal calculations for the Sticky Token Adjusted (Before and After) Total Supply occur automatically, based on the Sticky Token's behavior during the first unglue interaction. This interaction allows the contract to learn several key aspects:

1. Whether the token is burnable
2. If it allows transfers to the DeAd address
3. For ERC20 tokens, whether it complies with OpenZeppelin standards for calculating totalSupply (If an ERC20 token doesn't comply with these standards, the calculation will account for address(0)).

<aside> 🧠

In essence, Glue self-learns the Sticky Token's behavior during the first interaction, optimizing internal calculations for precision and cost-efficiency. These calculations require no developer knowledge and don't alter any behavior—it simply works out of the box. To know more: Read Sticky Token Self-Learning Settings

</aside>