Building Transparent Systems for Content Creators
We started in 2019 because content creators deserved better infrastructure. The media landscape was changing fast, and blockchain offered solutions that traditional systems couldn't match.
How We Got Here
Our founder spent five years working with independent journalists who struggled with fair compensation. Payment delays, unclear attribution, content theft—these weren't edge cases. They were daily realities.
In 2019, we started building tools that made sense for actual creators. Not theoretical blockchain applications, but practical systems that solved real problems. Things like timestamped content verification and transparent royalty distribution.
The Seoul digital media community gave us early feedback. We learned quickly what worked and what didn't. Turns out, creators care less about underlying technology and more about whether their work gets properly credited and compensated.
What Guides Our Work
We've built our approach around principles that matter in the real world of content creation and distribution.
Creator-First Design
Every tool we build starts with creator workflows. If it adds complexity without clear benefit, we don't ship it. Our verification systems run in the background—creators shouldn't need to think about them.
Transparent Operations
When a creator asks where their payment is or who's using their content, they get clear answers. No vague explanations or hidden processes. Our blockchain implementations exist to make things clearer, not more obscure.
Practical Innovation
We explore new approaches when they solve actual problems. Smart contracts for royalty splits? Yes, because they eliminate disputes. Blockchain for every tiny interaction? No, because that's wasteful.
Dirk Svendsen
Technical Director
Dirk joined us in 2021 after working on distributed systems at a fintech startup in Copenhagen. He'd grown frustrated watching talented engineers build complex solutions that users found confusing.
At sparkglowcharge, he leads our technical architecture with a focus on simplicity. His team built our content verification layer that processes attribution checks in milliseconds—fast enough that creators never notice the system working.
What I appreciate about Dirk's approach is his insistence on testing with real users before finalizing any feature. He's killed more "cool ideas" than anyone else on the team, usually because they didn't pass the practical use test.
Our Development Process
We've refined how we build tools based on feedback from hundreds of content creators across different media types.
Research Current Workflows
Before writing any code, we spend time watching how creators actually work. What tools do they already use? Where do existing systems fail them? We document pain points through direct observation, not assumptions.
Build Minimal Solutions
We create the simplest version that addresses the core problem. Our first content verification prototype had three buttons and one text field. It worked, and creators understood it immediately. That's when we knew we were on the right track.
Test With Real Users
Every quarter, we run workshops with independent journalists, videographers, and digital artists. They break our tools in ways we never anticipated. Those sessions have prevented countless poor design decisions from reaching production.
Recent Projects
