A program deployed to QRL 2.0's EVM-compatible chain. It has its own address, its code is fixed once deployed, and anyone can call it. The original QRL chain is Proof-of-Work with no virtual machine, so contracts exist only on QRL 2.0.
What does 'source verified' mean — is it audited?
Source-verified means someone submitted source code that compiles to the exact deployed bytecode, so you can read what the contract does. It is NOT an audit or a safety guarantee — verified code can still be malicious or buggy.
Why might the events list be empty?
Event logs are indexed going forward. A contract deployed before log indexing began, or one that simply hasn't emitted events, will show none even though it exists.
This contract is a token — where are its holders?
When a contract implements a token standard (QRC-20/721/1155), its supply, holders and transfers live on the linked token or NFT page.