@DeOpenSourceGuyi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- Web
Account-level information from X, not a live location or the device used for a specific post.
Somewhere in CA
Joined July 2023
- Tweets3.1K
- Following795
- Followers779
- Likes2.8K
Pinned Tweet
I’m running for the Intersect Board because I believe I have both a responsibility to what we started and an obligation to help ensure Intersect succeeds.
My history with Intersect goes back to before Intersect existed, when the work was still being developed through the original Cardano DCF workstream. I helped lead the original design, drafted the first charter, and became the first employee contracted onto the organization.
From there, much of my focus was building the technical foundations Intersect would need for the long term. I helped establish the Technical Steering Committee and Open Source Committee, drafted their complementary remits, built out the security function, established the bug bounty program, and helped create the structures needed for technical stewardship beyond simple administration.
But my focus was never just on committees. It was on making Intersect function like a proper Member-Based Organization.
With support from the community, I established Intersect’s incubation program and began building project support services around the needs of builders. We introduced legal support and other professional services that projects could access at no cost. I worked to get accelerator programs off the ground, coordinated developer advocacy efforts intended to improve onboarding and help projects navigate the ecosystem, and continually looked for ways Intersect could become a place where projects were supported rather than simply processed.
The Open Source Committee became the first committee to procure services, develop a formal strategy and white paper, secure funding against that strategy, and then deliver against it. Much of that work was accomplished by a two-person team, and I remain incredibly proud of what we proved could be accomplished with a clear mandate, disciplined execution, and very little bureaucracy.
I also made a deliberate effort to engage with our industry peers outside Cardano. I sought those relationships out because I believed then, and still believe now, that an MBO responsible for supporting one of the world’s largest decentralized ecosystems should not operate in isolation. We should be learning from other foundations, open source organizations, standards bodies, and ecosystems, while also showing them what Cardano is capable of.
We have a tendency to become isolationist when we simply do not need to be.
If elected to the Board, I will continue building those bridges.
Eventually, I stepped away because I believed much of this work needed to belong to the community rather than to me. Since then, I have continued supporting projects across Cardano and currently serve as Vice Chair of the Technical Steering Committee. Being outside the organization has also given me a different perspective on the frustrations members, builders, committees, and stakeholders experience.
That is a major reason I am running.
Intersect should not disappear. It should not become irrelevant. It should not exist simply to administer processes created for their own sake.
It should be a strong member-based organization that enables Cardano’s technical stewardship, supports the people doing the work, creates room for community initiatives to grow, and operates with enough focus that small teams can produce meaningful results.
I know the history behind Intersect because I helped write part of it. I know the internal challenges because I worked through them. I know the external frustrations because I experience them now. And most importantly, I know how to take an idea, build the structure around it, and get it delivered.
I also support Jack and believe leadership needs a Board that gives him the coverage, challenge, and support required to execute effectively. Some problems can be solved from the outside. Others require decisions from the top. If politics continues to outweigh execution, Intersect will struggle. The Board has an important role in changing that.
Cardano will always be closely associated with Charles Hoskinson’s legacy. In a much smaller way, Intersect is part of mine. I helped build it from its earliest days, and I care deeply about seeing the original promise fulfilled.
I’m not running to preserve Intersect as it is.
I’m running because I believe Intersect is worth fixing, worth focusing, and worth fighting for and because I know we can make it effective again.
Christian Taylor retweeted
For community awareness, new operator and a new ticker don't mean a new owner.
The existing pool IDs remain the same, the delegations don't have to move, and operational control can simply be transferred by providing Shunsuke with the existing cold private keys.
That's pretty much it.
Unless the ownership of the pools has actually changed, which nobody outside the parties involved could independently prove anyway, since there is no way to know whether copies of those keys are still retained, changing the operator or ticker doesn't change who owns the underlying pools.
And that's what makes the whole announcement a little confusing to me. Why make such a big statement about “transferring” the pools when, technically, what appears to have happened is that the existing cold keys were copied and provided to a new operator?
The delegations don't need to move precisely for that reason.
And of course, the decision to do this instead of having Shunsuke create his own stake pools and transferring the delegations EMURGO actually controls to those new pools tells us something too.🤨😮💨
Hopefully those keys, nor their encrypted versions, were ever exposed through an insecure or hot environment during the "transfer". 🤞
An update on the EMURGO and @YoroiWallet stake pools:
As referenced in our previous posts regarding EMURGO’s withdrawal from Cardano governance, including our decision to step back following the SecondFi security incident and our intention to de-register as a Cardano DRep, we are making a few operational updates.
Operational control of the EMURGO and Yoroi stake pools (EMURGO 1, EMURGO 2, EMURGO 3, EMURGO 4, EMURGO 5, EMURGO 6 and YOROI) has been transferred to Shunsuke Murasaki (@MurasakiCardano). Many in the community will know Murasaki as a long-time member of the Cardano community, with especially strong ties in Japan, Indonesia, and Singapore, as well as an early employee at EMURGO before leaving earlier this year to pursue new adventures. We have full faith in his integrity to Cardano over the long term.
These updates have been processed operationally and will be formally reflected onchain in coming days.
Key details for delegators:
- No action required: Delegations and staking rewards continue uninterrupted, and existing delegations carry over automatically.
- Unchanged pool IDs: Pool IDs remain identical. Murasaki will share a separate confirmation regarding any upcoming changes to the pool names and tickers.
- Non-custodial staking: As always, staking on Cardano remains entirely non-custodial, leaving delegators free to re-delegate to any pool whenever they choose.
Christian Taylor retweeted
【EMURGOのステークプールを引き継ぎました】
皆様、お久しぶりです。村崎です。
7年間勤めたEMURGOを6月初旬に退社し、新たな挑戦を始めています。
カルダノに携わった7年で、多くの方々と一緒に仕事をすることができました。退社後もそのご縁は続いており、複数のプロジェクトを支援しています。
An update on the EMURGO and @YoroiWallet stake pools:
As referenced in our previous posts regarding EMURGO’s withdrawal from Cardano governance, including our decision to step back following the SecondFi security incident and our intention to de-register as a Cardano DRep, we are making a few operational updates.
Operational control of the EMURGO and Yoroi stake pools (EMURGO 1, EMURGO 2, EMURGO 3, EMURGO 4, EMURGO 5, EMURGO 6 and YOROI) has been transferred to Shunsuke Murasaki (@MurasakiCardano). Many in the community will know Murasaki as a long-time member of the Cardano community, with especially strong ties in Japan, Indonesia, and Singapore, as well as an early employee at EMURGO before leaving earlier this year to pursue new adventures. We have full faith in his integrity to Cardano over the long term.
These updates have been processed operationally and will be formally reflected onchain in coming days.
Key details for delegators:
- No action required: Delegations and staking rewards continue uninterrupted, and existing delegations carry over automatically.
- Unchanged pool IDs: Pool IDs remain identical. Murasaki will share a separate confirmation regarding any upcoming changes to the pool names and tickers.
- Non-custodial staking: As always, staking on Cardano remains entirely non-custodial, leaving delegators free to re-delegate to any pool whenever they choose.
Intersect is at a turning point. This election will help decide whether it remains a status-quo organization that fades from relevance, or whether it finally forms a clear identity as a true member-based organization and builds toward lasting success, in the spirit of what the LFDT has achieved.
Intersect has delivered important work. Those results still do not, on their own, justify the current level of funding in the eyes of much of the community. Membership has fallen from 2–3k to just over 600. At $10 per membership, that decline is a clear signal: the organization has not yet earned durable member trust.
What Intersect needs now is operational expertise in running an MBO—not only community relations, and not only Cardano technical knowledge. It needs people who understand how to steward a nonprofit that delivers real member benefits, curates an ecosystem, and practices genuine open source.
To date, Intersect has only partly fulfilled those roles. Budget management and hard forks matter, but they are not the whole purpose of the organization, and they cannot be its only focus. The foundations still need to be planted.
I previously helped design and pilot the core functions Intersect needs in order to stabilize and grow. Much of that work has not been carried forward, and the ecosystem has felt the gap. If elected, I will put the connections, resources, and operating experience I have built over the past several years in service of the staff and the organization, so Intersect can deliver for members and set itself up to succeed. It is time to set the politics aside and see how bad the scarring on the hull really is….
Being on the outside I truly do see it and can guarantee I have more skin in this to see intersect succeed then most
Might be hope at Xbox in a few ways for the frAnchises, layoffs stink for those affected but so happy Halo studios got shutdown, ever since bungie departure the game and franchise lost its meaning and story, not to mention art style.
Now o just hope Treyarch / Sledgehammer don’t call of duty the halo franchise, but it would be nice to get a grounded story in the real life situation of halo, similar to some recent modern warfare’s, like what reach attempted to do
I see crypto going through stages like the Open Source Movement did way back when .
Philosophies, regulation, profit versus idealism, and technical innovation all colliding to build a new system that will create massive integration into our daily lives.
After that movement, Open source now already sits inside 96% of modern software after a few decades.
In a few years time, with Quantum, bad actor practices, and AI threats, but government management of their own base currencies, blockchain may be the only single source of truth and defensible right to privacy in the near future.
I’ve been in the room since before Intersect had a name. I helped shape the original MBO vision, built programs to support projects and maintainers, strengthened open source and security practices, and pushed Intersect to engage with the wider industry instead of becoming isolated inside Cardano. I know where the organization started, where it drifted, and where it can still go.
I’m running because Intersect needs to get back to being a member-led organization that delivers real value, not more process for the sake of process. I’ll push for stronger technical stewardship, less bureaucracy, better support for builders, and greater independence. I’m not interested in protecting the status quo. I’m interested in protecting what the community has invested in and making Intersect worth believing in again. The change must start at the top or there won't be an Intersect for next year.
Intersect Board elections 2026 🗳️
The final countdown!
Just 48 hours remain before voting closes for the Intersect Board elections on Friday, September 25 at 12PM UTC.
Verified Individual and Enterprise Members, cast your votes in the Members Area.
members.intersectmbo.org
Christian Taylor retweeted
solid month in the @cardano universe 👀
first, thirteen teams through @draper_u’s Genesis program earlier this month
then, eight teams announced for the Cardano Accelerator Program through @cardano_CF’s Venture Hub
twenty-one teams getting support to turn their work into businesses that last
add @alphagrowth1’s @Cardano_Prime ambitions for DeFi, and @OrionFund’s work helping founders prepare to scale and attract investment
more practical ways for builders to get backing, find their footing and reach actual users
and then…at last this week, Catalyst
nearly a year since fund14 results that minted on oct 10 then, the next Catalyst pilot cohort is heading for the launchpad
to everyone who put their work forward, and everyone who helped us get here: thank you
been a helluva ride. feels like a century
but it’s [seatbelts] on 🚀
Christian Taylor retweeted
Today we're open-sourcing #CaptainCode 🚀 🫶
Captain picks the right AI model for each prompt and runs it from one terminal, on your machine. It drives the @claudeai Code, @OpenAI Codex, @xai @grok and @Cursor CLIs you already pay for, and gives you access to the most capable open-weight models through @OpenRouter, @nvidia NIM and @huggingface.
Why we built it? We no longer knew which model to use for what, we were under-using our subscriptions, and we wanted to hand more work to cheaper, capable open models. More than 25% of my prompts go to open-weight models as a result, and counting!
How does Captain work? It leverages the newly released @typesafeai Jev model to triage every task in milliseconds. Then it routes on quality, cost and latency, with the outcome logged locally for iterative improvements. When a model hits its usage limit, it reads the reset time and carries the work, context included, to the next relevant available model. When you type /oss, the task goes to open models only.
Learn more about Captain, try it now: captaincode.ai
We welcome feedback and contributions 🖖
Crafted with ❤️ on @opencode.
Never thought I'd reach a point in my life that my bad typing proves I'm a real person online.
After being scolded so much in my computer lab classes, who laughing now!
Christian Taylor retweeted
I’m running for the Intersect Board because I believe I have both a responsibility to what we started and an obligation to help ensure Intersect succeeds.
My history with Intersect goes back to before Intersect existed, when the work was still being developed through the original Cardano DCF workstream. I helped lead the original design, drafted the first charter, and became the first employee contracted onto the organization.
From there, much of my focus was building the technical foundations Intersect would need for the long term. I helped establish the Technical Steering Committee and Open Source Committee, drafted their complementary remits, built out the security function, established the bug bounty program, and helped create the structures needed for technical stewardship beyond simple administration.
But my focus was never just on committees. It was on making Intersect function like a proper Member-Based Organization.
With support from the community, I established Intersect’s incubation program and began building project support services around the needs of builders. We introduced legal support and other professional services that projects could access at no cost. I worked to get accelerator programs off the ground, coordinated developer advocacy efforts intended to improve onboarding and help projects navigate the ecosystem, and continually looked for ways Intersect could become a place where projects were supported rather than simply processed.
The Open Source Committee became the first committee to procure services, develop a formal strategy and white paper, secure funding against that strategy, and then deliver against it. Much of that work was accomplished by a two-person team, and I remain incredibly proud of what we proved could be accomplished with a clear mandate, disciplined execution, and very little bureaucracy.
I also made a deliberate effort to engage with our industry peers outside Cardano. I sought those relationships out because I believed then, and still believe now, that an MBO responsible for supporting one of the world’s largest decentralized ecosystems should not operate in isolation. We should be learning from other foundations, open source organizations, standards bodies, and ecosystems, while also showing them what Cardano is capable of.
We have a tendency to become isolationist when we simply do not need to be.
If elected to the Board, I will continue building those bridges.
Eventually, I stepped away because I believed much of this work needed to belong to the community rather than to me. Since then, I have continued supporting projects across Cardano and currently serve as Vice Chair of the Technical Steering Committee. Being outside the organization has also given me a different perspective on the frustrations members, builders, committees, and stakeholders experience.
That is a major reason I am running.
Intersect should not disappear. It should not become irrelevant. It should not exist simply to administer processes created for their own sake.
It should be a strong member-based organization that enables Cardano’s technical stewardship, supports the people doing the work, creates room for community initiatives to grow, and operates with enough focus that small teams can produce meaningful results.
I know the history behind Intersect because I helped write part of it. I know the internal challenges because I worked through them. I know the external frustrations because I experience them now. And most importantly, I know how to take an idea, build the structure around it, and get it delivered.
I also support Jack and believe leadership needs a Board that gives him the coverage, challenge, and support required to execute effectively. Some problems can be solved from the outside. Others require decisions from the top. If politics continues to outweigh execution, Intersect will struggle. The Board has an important role in changing that.
Cardano will always be closely associated with Charles Hoskinson’s legacy. In a much smaller way, Intersect is part of mine. I helped build it from its earliest days, and I care deeply about seeing the original promise fulfilled.
I’m not running to preserve Intersect as it is.
I’m running because I believe Intersect is worth fixing, worth focusing, and worth fighting for and because I know we can make it effective again.
This is no longer a Cardano account, this is now dedicated to useless facts about hats starting below:
"Arizona-style cowboy hats traditionally feature wider brims than northern versions (better sun protection in the desert) and a peaked crown that helps keep the head cooler."
@adamKDean
Lessons in Cardano givernance #3:
If the community paid taxes to a bucket and that bucket funded anything you do, it's taxpayer money.
$ from Cardano transactions goes to Treasury, treasury $ to catalyst, catalyst $ to project = taxpayer funded project
Intersect funded by treasury = taxpayer funded organization
Cardano Summit funded by treasury = taxpayer funded event
Just becasue you ahve a fancy title or a different process stemming from another process, they tag on the shirt still says "Made in Cardano Treasury"
That means you need to treat that funding with respect and the transparency taxpayer deserve, let's not act like governments once they collect they're taxes, we built better systems for this reason.
It's simple, same inputs same outputs.
I’m running for the Intersect Board because I believe we need a different approach if we want different results.
My focus is simple: protect the investments already made in Intersect, put community interests ahead of internal politics, and help move the organization forward without tearing down what works.
I’m not interested in chaos or political games. I’m interested in practical governance, technical stewardship, accountability, and making Intersect work for its members again.
That’s what I intend to bring to the Board.
Christian Taylor retweeted
🧵Turn a machine into a paid Filecoin storage node in five minutes.
TL;DR: Curio PDP now ships as one Docker Compose stack. One command installs the chain node, database, and storage node, then a guide walks through funding a wallet and registering with Filecoin Onchain Cloud.
Christian Taylor retweeted
Anyone still needing to upgrade, check out the latest on the Intersect Github. Edge nodes and infrastructure nodes may benefit from the upgrade too.
Link: github.com/intersectmbo/card…
Christian Taylor retweeted
This, but for a Science lab
Christian Taylor retweeted
The Radix Foundation has published its Public Incident Report: Vault-Authorisation Vulnerability and Loss of Network Liveness.
The report provides a detailed account of the incident, including the vulnerability, its impact, how it was contained, and the remediation and security measures implemented.
Read the full report:
radixdlt.com/blog/public-inc…
👇💯
The parameter committee has spent months/years debating on how to accurately gauge SPO sentiment about raising stakePoolTargetNum from 500->1000.
As part of this, myself and another member of the parameter committee meticulously drafted all the arguments for and arguments against and linked them in separate documents so that voters could have a balanced view of both arguments. We linked these inside of a neutral-language Info Action body for SPOs to consider.
Because Info Actions have no ratification threshold and stakePoolTargetNum isn't a parameter that SPOs vote on through governance, the parameter committee collectively agreed to use a specific threshold of explicit YES > explicit NO for this Info Action. This is already above and beyond what the protocol and the Constitution require and we went out of our way to give SPOs a voice on this.
Unfortunately, a community member who is opposed to the parameter change hijacked our draft and the years of effort that went into it, changed the threshold to suit his desired outcome, and submitted it without consulting anybody.
Even if the we can reasonably disagree about what the threshold should be for this vote (remember it is not required at all), taking other people's work, twisting it, and submitting in a manner to suit your own narrative is extremely disappointing to see.
I'm very disheartened by this after having spent years of my own, uncompensated effort building to this point only to see a community member undermine it like this.
If you want to see the real draft that the parameter committee put together, you can read it here. Also the case for and case against are linked as well, so you can see both sides of the discussion fairly.
I can't speak on behalf of the others, but I will be interpreting the outcome of the vote based on the criteria that the parameter committee collectively agreed on, regardless of what this Info Action says.
docs.google.com/document/d/1…