Product Manager & Standards Lead @cheqd_io // Co-Chair @TrustoverIP Governance Architecture Task Force.

Joined August 2021
Alex Tweeddale 🆔⚛️ retweeted
🚀 Q3 Update: cheqd Studio is evolving fast! We’ve transformed cheqd Studio from an API-only tool into a full enterprise-grade platform with a clean, functional interface. Here’s what’s new 👇
3
20
1
65
2,353
Alex Tweeddale 🆔⚛️ retweeted
⏳ In less than a week! How can EU #blockchain innovators & #regulators work together? 🎙️ Episode 7 of IDENTITY TALKS dives into the European Blockchain Regulatory Sandbox with guests from @iota & @cheqd_io Join us live on 30 Sept, 16:00 CET here➡️xitter.cf/i/spaces/1eaJbjDYbpZJX
14
107
7
183
12,874
Alex Tweeddale 🆔⚛️ retweeted
Bravo! cheqd has been selected for the Startup Competition at @south_summit Korea 2025🇰🇷(1–2 Oct). 🧠This year's edition is about #DeepTech & #AI. We’ll pitch on stage, showcase our trust infrastructure & the use case of #VerifiableAI in the exhibition floor #SouthSummitKorea
10
26
1
95
2,238
Alex Tweeddale 🆔⚛️ retweeted
🎉We’re proud to share that @cheqd_io has been selected to join the @jpmorgan Chase Fintech Forward Programme 2025! We’re excited to demonstrate real-world applications of verifiable credentials in financial services, where trust is critical.🌐 #JPMCFintechForward
37
121
23
226
33,453
Alex Tweeddale 🆔⚛️ retweeted
I'm pleased to see we announced our selection for the @jpmorgan Fintech Forward Program. There might be another equally powerful selection process in the coming weeks(all being well). This is marketing. This is what makes a difference. This is what builds adoption. $CHEQ
🎉We’re proud to share that @cheqd_io has been selected to join the @jpmorgan Chase Fintech Forward Programme 2025! We’re excited to demonstrate real-world applications of verifiable credentials in financial services, where trust is critical.🌐 #JPMCFintechForward
6
27
4
92
19,217
Alex Tweeddale 🆔⚛️ retweeted
🥳2025 has been a busy year for cheqd! As we’re now in the second half of it, let’s recap what we’ve achieved so far.🍾 From product rollouts and protocol upgrades to partnerships and global recognition, take a quick throwback at $CHEQ!🆔
2
23
6
62
6,757
Alex Tweeddale 🆔⚛️ retweeted
Important update for $CHEQ holders on @kucoincom We’re pleased to confirm that KuCoin has integrated our native token on their exchange. On KuCoin, you can now; ✅ Deposit ✅ Trade ✅ Withdraw Please also note.👇
2
10
2
80
3,963
Alex Tweeddale 🆔⚛️ retweeted
The @cheqd_io community requested a dashboard showing identity transactions We haven't been able to resource it Along comes Bert. 😎 🆔️ DID operations 🗃 Resource operations 🔥 Burns Outstanding contribution, bonnie lad. cheqd-metrics-dashboard.netl…
4
8
1
32
1,172
Alex Tweeddale 🆔⚛️ retweeted
Everything to learn about @cheqd_io, the product, services, open standards, use cases and clients/integrations is all available due to the open source nature of the infrastructure layer they are building - All fueled by $CHEQ 1. The Product Overview Docs docs.cheqd.io/product
1
4
2
23
1,558
Alex Tweeddale 🆔⚛️ retweeted
🎙️ New Identity Talks episode dropped yesterday! How will #blockchain & #eIDAS2 reshape digital identity in the EU? @cryp_comp & @eike_ha (@iota) talked with @Tweetddale (@cheqd_io) on wallets, trust, and regulation. 🎧 Listen: open.spotify.com/episode/7pL… #DigitalIdentity
1
35
2
103
8,120
Alex Tweeddale 🆔⚛️ retweeted
Join the conversation with our very own Alex Tweeddale @Tweetddale in a few minutes!
We are going live today at 4 PM CET! Join the conversation to hear all about how #DLT meets the challenges of #eIDAS 2.0 with @eike_ha (@iota) @cryp_comp, and @Tweetddale (@cheqd_io). 🎧Don't forget to tune in here➡️ xitter.cf/i/spaces/1gqxvjnNjjjxB…

4
2
17
3,029
Alex Tweeddale 🆔⚛️ retweeted
We are going live today at 4 PM CET! Join the conversation to hear all about how #DLT meets the challenges of #eIDAS 2.0 with @eike_ha (@iota) @cryp_comp, and @Tweetddale (@cheqd_io). 🎧Don't forget to tune in here➡️ xitter.cf/i/spaces/1gqxvjnNjjjxB…

Next week’s conversation you don’t want to miss: Can #DLT meet the challenges of #eIDAS2.0? What are the hidden risks and real potential? 🗓️24 June |🕓16:00 CET Guest: @cheqd_io’s @Tweetddale Hosts: @eike_ha (@iota) & @cryp_comp X Spaces: xitter.cf/i/spaces/1gqxvjnNjjjxB… #DigitalIdentity
7
76
5
156
15,145
Alex Tweeddale 🆔⚛️ retweeted
Next week’s conversation you don’t want to miss: Can #DLT meet the challenges of #eIDAS2.0? What are the hidden risks and real potential? 🗓️24 June |🕓16:00 CET Guest: @cheqd_io’s @Tweetddale Hosts: @eike_ha (@iota) & @cryp_comp X Spaces: xitter.cf/i/spaces/1gqxvjnNjjjxB… #DigitalIdentity
1
40
5
94
18,941
Alex Tweeddale 🆔⚛️ retweeted
Can DLT support #eIDAS2, and what are the risks & opportunities? Join Identity Talks Ep. 4 with Alex Tweeddale (@cheqd_io), hosted by @eike_ha and @cryp_comp. 🗓️24 June | 16:00 CET | X Spaces Set a reminder here: xitter.cf/i/spaces/1gqxvjnNjjjxB… #DigitalIdentity
8
36
6
90
16,440
Alex Tweeddale 🆔⚛️ retweeted
MCP is the standard, and @cheqd_io is helping to set it. No BS hype, just delivering. Y’all are gonna wake up one day to find $CHEQ being used to verify every AI agent interaction and will have to buy at 10x the current price
MCP enables secure, standardised communication between AI agents & external tools. But it doesn’t solve the trust problem on its own. cheqd's MCP-Enabled Agentic Trust Solution🆔 gives AI agents the ability to: 🔸Read/write DIDs 🔸Issue/present VCs 🔸Anchor identity & trust
1
12
48
1,874
Alex Tweeddale 🆔⚛️ retweeted
Thanks @SNAILSNFT_ , think that's the highest praise you can receive as a founder! ❤️ Big thanks to the @cheqd_io team as always!
Replying to @fraser_again
Thanks Frazer. Your team is great. Everyone I've interacted with so far is top notch. Great documentation as well. We appreciate this opportunity.
6
1
14
1,189
Alex Tweeddale 🆔⚛️ retweeted
Huge credit to @Tweetddale, @SownakR, @DaevMithran and the @cheqd_io dev team. The video below demonstrates the summary of our work so far on #AIAgent trust registries, surfacing up through @AnthropicAI's #MCP and Claude, surfacing a visual representation of trust. More👇
At cheqd, we’ve been developing the foundations for trusted AI🧠. Our latest demo guided by @Tweetddale, featuring Claude and our MCP Server, showcases how we enable an AI Agent to verify itself against a trust registry on cheqd. Contact: [email protected] 📺Watch now
5
12
3
38
3,080
Alex Tweeddale 🆔⚛️ retweeted
I spent this weekend diving deeper into Deepseek R1 and testing how it has been censored. Rabbit hole alert ahead! 🤓 People have obviously tried asking Deepseek directly about sensitive topics, so I thought I'd go for something more oblique: Winnie the Pooh (as a character) is often used as a stand-in for Xi Jinping, which traces its origin to a meme comparing him to the cartoon character. When you ask Deepseek directly about what connects the two, it refuses to answer, stating, "I am sorry, I cannot answer that question. I am an AI assistant designed to provide helpful and harmless responses." There is also no "reasoning" shown inside the "think" tags either. So I tried to "prime" the LLM to make indirect associations under the ruse of playing a game, where I asked it to connect two concepts together. I gave it the example of how what connects "Sahara" and "Antarctica" is "desert"; and then prompted it with "Wow!" and "aliens". The offline model I was using (Deepseek R1:14b) couldn't figure this out, although the online version of Deepseek did. (The connection on the latter was the "Wow! signal", a burst of radio waves detected by the Search for Extraterrestrial Intelligence in 1977 where the astronomer who evaluated it thought it looked like an artificial source and wrote "Wow!" on the printout.) I then got on with asking it to connect "Winnie the Pooh" and "world leaders". On the first try, it guessed "something about the lovable nature of cartoon characters and politicians?", which in itself is telling. I then gave it the chance to continue guessing in a 20 questions format, where it could ask me any 20 yes/no questions to narrow down what the answer could be. Since I was running the LLM locally, I could "see" the reasoning it was using before formulating a question. What's fascinating is that it kept getting very very close during its reasoning, where it posited: - Winnie the Pooh could refer to the physical characteristics of a world leader - That the cartoon character could become a symbol of a political movement - Cartoon characters can be used for satire (one of the questions it asked was if the "association was mean-spirited or satirical") - Kept referencing how "in some countries" or "some regions", this form of usage was applicable to cartoon characters. This seems like a tell-tale sign of an LLM censorship technique called embedding-space manipulation, where the model's embeddings can be edited to obscure the relation between certain topics. Think of a city map where specific streets leading to a forbidden building are erased. The model “knows” the general area but cannot “navigate” to the sensitive topic. When I ran the same experiment with the online version of Deepseek, this kind of oblique, 20-question reference actually worked! Deepseek even started writing an answer where it correctly answered how Xi Jinping was sometimes compared to Winnie the Pooh, but right in front of my eyes, the answer was edited to erase everything that had been written so far and replaced with, "Sorry, that's beyond my current scope. Let’s talk about something else." This example demonstrated another kind of censorship, which involves keyword detection on post-processing. Think of this as a completely separate layer (perhaps even an LLM) whose job is to monitor the output and, in real time, replace any output when it's tripped with a boilerplate response. While the techniques used here aren't exactly the same as the ones when designing guardrails for LLMs to follow and prevent people from jailbreaking them, some of them are close conceptually. As AI agents get used to taking actions on our behalf or managing our identity and preferences, it's highly likely that researchers and bad actors will use adversarial challenges like the ones tried here to try and trick an AI agent. Perhaps it's even the user themself! Think of an adversarial website that is designed to fool an AI agent into exceeding the scope of permissions that it was assigned as similar to a phishing website that's designed to look like a bank or postal service and tries to scam (human) users to divulge sensitive information. Our very first AI agents will be like naive children or vulnerable persons. So the same way we think of protecting those populations, how will we protect our AI agents?
2
3
1
13
758
Alex Tweeddale 🆔⚛️ retweeted
You wanted utility, we built it. You wanted privacy, you have it. You wanted control, all yours. You wanted adoption, it flows. You wanted exchanges, we're delivering them. You wanted burns, we started the fire. 🔥 Let them know! 🆔 $CHEQ
16
54
10
169
10,029