When I started freelancing from home, my salary was fixed at 100 USD a month. The job was simple and written down: put content on the website, and maintain it. Nothing in that agreement said I'd do anything beyond that.
A month in, my boss bought a domain and told me: build this website. I barely knew how to use AI back then — but I pushed through, wrote the HTML, CSS, JavaScript, and got her site live. I was proud. My reward? Nothing. When I reminded her, she said: "This is part of your job. It doesn't matter."
After that came full tables of contents, anchor links jumping to exact chapters on click — task after task, none of it in my original scope. On freelance marketplaces, each of those small tasks would typically be billed at 10–15 USD. She got them for free — using my leniency against me.
The whole problem was simple: the rules of my work existed only in words, not in anything that actually held. So they were bent the moment it suited someone else. I kept thinking: I wish the do's and don'ts had been written into something binding from day one — so my rights couldn't just be erased.
That's the exact gap @Dusk 's XSC standard is designed to address — but for regulated financial assets. The idea is that key rules governing an asset — who can hold it, how it can be transferred, and what disclosures may be required — can be encoded into the asset's compliance framework and enforced by the protocol, rather than relying solely on a separate document. The goal is for compliance requirements to remain attached to the asset's transfer and lifecycle rules, rather than existing only as a separate promise.
Honest take — this is for on-chain securities, not freelance contracts, and it's still early and complex to build. But for someone whose "rules" were only ever words that got bent, the idea of rules that actually hold is worth a lot.
Follow the signal, not the noise.
$DUSK #dusk @Dusk
A month in, my boss bought a domain and told me: build this website. I barely knew how to use AI back then — but I pushed through, wrote the HTML, CSS, JavaScript, and got her site live. I was proud. My reward? Nothing. When I reminded her, she said: "This is part of your job. It doesn't matter."
After that came full tables of contents, anchor links jumping to exact chapters on click — task after task, none of it in my original scope. On freelance marketplaces, each of those small tasks would typically be billed at 10–15 USD. She got them for free — using my leniency against me.
The whole problem was simple: the rules of my work existed only in words, not in anything that actually held. So they were bent the moment it suited someone else. I kept thinking: I wish the do's and don'ts had been written into something binding from day one — so my rights couldn't just be erased.
That's the exact gap @Dusk 's XSC standard is designed to address — but for regulated financial assets. The idea is that key rules governing an asset — who can hold it, how it can be transferred, and what disclosures may be required — can be encoded into the asset's compliance framework and enforced by the protocol, rather than relying solely on a separate document. The goal is for compliance requirements to remain attached to the asset's transfer and lifecycle rules, rather than existing only as a separate promise.
Honest take — this is for on-chain securities, not freelance contracts, and it's still early and complex to build. But for someone whose "rules" were only ever words that got bent, the idea of rules that actually hold is worth a lot.
Follow the signal, not the noise.
$DUSK #dusk @Dusk