ORIGYN 🇨🇭 engagement report
@ORIGYNTech - 65K followers on X
Measured over 2 original posts from a 30-day window, last computed on September 21, 2026.
Engagement
Early reading. We have captured 2 original posts for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.
A typical post picks up 125 interactions against 65K followers, an engagement rate of 0.189%. Posts are seen about 2.8K times each, and 4.40% of those impressions turn into an interaction. That is about 4.35% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.07 posts a day over the last 30 days, though only 7% of days saw any activity at all. Most posts go out around 05:00 UTC, and Wednesday is the busiest day of the week. Of the 2 posts sampled, 50% carry an image or video and 50% link out. The account's strongest tracked post pulled 3.2K interactions, about 25x its own typical post. Only 2 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
Measured over 2 original posts from a 30-day window, last computed on September 21, 2026.
Where this sits in the catalog
At 0.189%, ORIGYN 🇨🇭 sits above the 50th percentile of the 205,374 accounts in this comparison. That places it in the above the median band, which runs 0.143% to 0.678%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.004% |
| 25th percentile | 0.024% |
| 50th percentile | 0.143% |
| 75th percentile | 0.678% |
| 90th percentile | 2.55% |
| 99th percentile | 82.4% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 05:00 UTC, and Wednesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 89K |
| 01:00 UTC | -2% | 90K |
| 02:00 UTC | -3% | 88K |
| 03:00 UTC | -4% | 94K |
| 04:00 UTC | -5% | 76K |
| 05:00 UTC | -4% | 75K |
| 06:00 UTC | -5% | 86K |
| 07:00 UTC | -5% | 93K |
| 08:00 UTC | -4% | 108K |
| 09:00 UTC | -4% | 124K |
| 10:00 UTC | -3% | 129K |
| 11:00 UTC | -3% | 141K |
| 12:00 UTC | -3% | 154K |
| 13:00 UTC | -3% | 167K |
| 14:00 UTC | -4% | 173K |
| 15:00 UTC | -2% | 176K |
| 16:00 UTC | -3% | 171K |
| 17:00 UTC | -3% | 159K |
| 18:00 UTC | -2% | 149K |
| 19:00 UTC | -2% | 141K |
| 20:00 UTC | -1% | 131K |
| 21:00 UTC | 0% | 116K |
| 22:00 UTC | -2% | 100K |
| 23:00 UTC | -1% | 90K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 393K |
| Monday | +1% | 483K |
| Tuesday | -2% | 520K |
| Wednesday | -3% | 472K |
| Thursday | -2% | 430K |
| Friday | -3% | 447K |
| Saturday | +2% | 393K |
Formats this account uses
Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.
| Format | This account | Catalog effect | 95% interval | Accounts behind it |
|---|---|---|---|---|
| Image or video | 50% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 50% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | no effect | -2% to -1% | 42K |
- 50% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
- 50% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
- Its average post runs 185 characters, which falls in the 180 - 280 characters band. Across the catalog, posts of 180 to 280 characters match the same accounts' other posts almost exactly.
These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.
Best tweets
- May 10, 202625x their median
Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from https://t.co/D5Dfj44BmO. Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network (https://t.co/ptsshOm9nj) but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at https://t.co/lloVYiGYs8 shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on https://t.co/IfQrVovF3L can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!
- Jan 15, 20263.3x their median
https://t.co/vNSWDCmlac
- Aug 21, 20261.5x their median
Important information for both the ORIGYN DAO and Gold DAO ecosystems. The early Gold DAO contributing team has transferred 100 million $GOLDAO tokens to the ORIGYN DAO Treasury. These tokens remain fully staked with a 2-year maximum non dissolving delay, continuing to generate rewards. This strengthens both ecosystems: • ORIGYN DAO now holds 100M GOLDAO in its treasury, earning rewards in $OGY, $ICP, $GLDT, and $WTN. • These rewards are distributed to 5 year non dissolving $OGY stakers, further reinforcing long term participation. • Gold DAO also benefits through its 500M staked $OGY, receiving its share of the same reward pool. This is another step toward deeper alignment between ORIGYN DAO and Gold DAO, creating value for both communities.
- Aug 12, 2026
Digital Product Passports are becoming the foundation of trusted and transparent supply chains. With ORIGYN’s DPP infrastructure, businesses can meet upcoming EU regulations while providing verifiable authenticity and lifecycle data for every product. https://t.co/Xt5RoUd5H8
- Jul 14, 2026
🤩 @waibsummit was a fantastic opportunity to connect with the people shaping the future of digital assets. From Silvia’s talk on tokenization and ORIGYN Records to conversations with clients, partners, and the wider community, was full of valuable connections and ideas! $OGY https://t.co/pjaGYohIZL
- Nov 25, 2025
🎥 Watch the recap from @token2049 in Singapore! ORIGYN showed up strong, driving the RWA conversation and building awareness around on-chain certification with $OGY! If you’re curious what ORIGYN is all about, this video says it all! https://t.co/6cWbf8o0DC
- May 18, 2026
Digital Product Passports are becoming a reality in Europe. $OGY provides the infrastructure businesses need to adopt DPP in a simple, secure, and compliant way.👇 https://t.co/bxamwVzkTC
- Jan 30, 2026
📣 @caffeineai Contest Winners Announcement! Thank you to everyone who participated in the Caffeine x ORIGYN Challenge! We know this was not an easy task. Implementing both Caffeine and ICRC7 is advanced tech and indeed, most submissions did not meet all the technical requirements or expectations. But don’t worry, we anticipated this challenge would push boundaries, and we hope it helped you grow, learn, and have a bit of fun along the way. We’re confident that many of you will continue building within the ICP community, and that’s a win in itself! Now, while no project fully met both requirements, three projects stood out with impressive effort and potential. Each of these developers will receive $1000 $USDT: 🏆 Fran H. 🏆 Phasma F. 🏆 Omar Hernandez S. 🎉 Congratulations! You will soon receive an email from the ORIGYN Foundation, please respond to claim your reward. But that’s not all… To show our appreciation, all participants will receive $100 in $OGY tokens! To claim your reward, please send an email to [email protected] from the same address you used to submit your project, and include your Principal ID. Thanks again for taking on the challenge with us!
- Aug 3, 2026
Every ORIGYN digital certificate starts with $OGY! As the utility token powering the protocol, it’s used to mint certificates that secure authenticity, provenance, and ownership for real-world assets. Watch Silvia explain how it works 👇 https://t.co/HunyZkhNul
- May 4, 2026
ORIGYN is now featured on https://t.co/Q76imHus1E alongside brands like @Siemens and @AveryDennison! DPP is becoming a real market standard and $OGY is building an the most accessible infrastructure for Digital Product Passports. https://t.co/I7YGzvaOe8
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Buy or sell Twitter (X) accounts - escrow-protected
PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 125 interactions against 65K followers, an engagement rate of 0.189%. Posts are seen about 2.8K times each, and 4.40% of those impressions turn into an interaction. That is about 4.35% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.07 posts a day over the last 30 days, though only 7% of days saw any activity at all. Most posts go out around 05:00 UTC, and Wednesday is the busiest day of the week. Of the 2 posts sampled, 50% carry an image or video and 50% link out. The account's strongest tracked post pulled 3.2K interactions, about 25x its own typical post. Only 2 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
- What is ORIGYN 🇨🇭's engagement rate on X?
- ORIGYN 🇨🇭 (@ORIGYNTech) has an engagement rate of 0.189%, based on the median interactions across 2 original posts from the last 30 days against 65,412 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.189%, ORIGYN 🇨🇭 sits above the 50th percentile of the 205,374 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @ORIGYNTech have real engagement?
- There is not yet enough sample to rank this account against others of its size.
- When does @ORIGYNTech post?
- Most posts go out around 05:00 UTC, and Wednesday is its busiest day, at roughly 0.07 posts per day across the measured window.