Migrate to LUKSO
This page will overview the differences between building on the LSP ecosystem instead of regular wallets. You can find more information regarding the network and standards within the Introduction and Concepts & Glossary pages.
Things to watch out for
- Universal Profiles are smart contract accounts. This means, that the signer of the transaction is decoupled from the address of the account. EOA signatures can be verified off-chain, but checking their permissions requires an on-chain call to the Key Manager of the Universal Profile.
- The Universal Profile Browser Extension automatically handles permissions checks when interacting with dApps. If needed, signatures can be verified manually by retrieving the controllers of an account and checking their permissions.
- As developers interact with smart contracts with different or custom functionalities, verifying that certain conditions and methods are set before interacting with them is always recommended. Such checks can be done by detecting interfaces and metadata of the given address.
- When doing network interactions without a Transaction Relay Service, the controller of the Universal Profile has to be funded to execute network transactions on behalf of the account.
Deploying Ethereum Contracts to LUKSO
As LUKSO is EVM compatible, all smart contracts written for Ethereum can easily be ported over and redeployed. The main difference is that developers must connect to a LUKSO node or RPC endpoint instead of an Ethereum node.
If you want to do LSP smart contract deployments, interactions, or data retrievals, please check our developer tools, delivering all necessary functionality from ABIs to decoding and fetching.
You can read more about smart contract development in the following guides and pages: