Farage has just gone to the media to attack Restore Britain, again. He says that Elon Musk is supporting a party 'thatโs one man with a social media account.'
This is where Farage is so very wrong.
There are thousands and thousands and thousands of Restore Britain members, backed up millions of Brits who are with us.
Those numbers increase every day.
Farage can arrogantly insult me over and over, but he has never been more wrong.
Restore Britain is a team. This is a movement of millions of British patriots unlike anything that has ever been seen before.
This party isn't about me, it never has been. It is about our members, our people, our home. Not me. Them.
That is something he will never understand, and ultimately it's why he will lose.
The Restore Britain movement will win.
We are going to take our country back.
We are going to Restore Britain.
I can bet my kidney that Arsenal wonโt win the EPL trophy. Crystal Palace will humble them.
Pep will win his last league title this Sunday before he says goodbye to City fans.
Bookmark this!!
I am proud to announce local businesswoman Rebecca Shepherd as our Restore Britain candidate for the Makerfield constituency.
Rebecca has spent most of her adult life living and working in the Wigan borough, where she has built and run her own small business. Through that experience, she understands first-hand the pressures facing local businesses and working people across the community.
Like so many residents, Rebecca has seen the growing impact of rising costs, increasing legislation, red tape, and bureaucracy, which continue to make everyday life more challenging for ordinary people trying to work hard, support their families, and stay afloat.
Put simply - she understands what local men and women are going through.
This is the type of person we need in politics. Not career politicians, but genuine people with real life experience.
Rebecca is particularly passionate about improving SEND access and support across the local area. Her interest in SEND-friendly activities comes through the work she does within her Community Interest Company, where she has seen first-hand the importance of opportunities, practical support, and activities for people with additional needs.
Rebecca is standing for Makerfield because she believes local people deserve honest representation, accountability, and someone prepared to fight for the interests of the community rather than their own political careers.
I look forward to campaigning with Rebecca, and putting forward Restore Britainโs positive vision for the Makerfield constituency.
Rupert Lowe,
Restore Britain Leader
Our local priorities:
Safer streets for women and girls - tackling the gangs of foreign men who harass and intimidate local women and girls in Ashton, and elsewhere across the constituency and the Wigan Borough.
Fight reckless overdevelopment in areas including South Hindley, and Winstanley - roads, dentists and GPs must come before responsible house building provided for local families.
Improved SEND support for those in genuine need - we must avoid overdiagnosis, but also provide proper investment to those who need it. Including a constituency-wide investment programme for the improvement and maintenance of childrenโs playgrounds.
Tackle anti-social behaviour in Ashton and elsewhere - no-nonsense, visible policing to crack down on criminal activity in our towns. Parents too must be held responsible for what their children are inflicting on the community. We say enough is enough.
Restore our high streets - push for free car parking to drive footfall, abolish business rates to reinvigorate our town centres and deliver a full investigation into the explosion of vape shops and Turkish barbers for trading standards/immigration non-compliance.
We are in this to win it.
Say you lost half. Some people just lost half twice.
Here's a great coping mechanism. Say you bought Ethereum at $4k and it was around $2k now. You lost half.
Now imagine losing half twice, but of the original amount. If you serialize the loss so that the 2nd half lost is of a smaller, already lost half value, it doesn't work as well. That math, serialized would be 75% not 100%.
TLDR; A mental trick to feel better about losing everything, or almost everything. Reminder, BTC and ETH have both dropped 95% and gone on to make new all time highs, the trick is to stay in the game and keep fighting. Post explaining why PulseChain and other RH things has so much potential coming soon.
Rabby was the wallet I wanted to use. The simulator, the native DeFi tools, the way it got out of your way and let you use the chain. Then they dropped PulseChain support.
People kept using it anyway, half-broken, because nothing else came close. I thought about building a replacement. Honestly, I didn't want to.
I already run RPC nodes and data services for several PulseChain products, so the ops weren't the part that scared me. The moral weight of running a wallet itself was. People trust this kind of software to act consistently every time, and getting that wrong has different consequences than getting most other software wrong.
Then a well-known community member got drained. Using Rabby on PulseChain, in that half-broken state. The simulator was one of the things that stopped working when Rabby left. If it had still been alive that day, the malicious transaction would have flagged before signing. They would have seen the hack coming, and walked away.
I asked the obvious question: why are they still using Rabby? Other wallets objectively work better on PulseChain right now. Then I looked at my own Chrome extensions. Why am I still using Rabby too?
Because it's the wallet I want to use. The wallet I wish worked the way it did before.
Cappy is that fix. I am keeping everything that made Rabby good, and rebuilding the parts #PulseChain needs.
@Prawcin Truth is stranger than fiction
This clip was about the UK allowing a literal terrorist back in the country who said they wanted to kill white people and jews
The caption is accurate
Think about how bad it is that, while this seems ridiculous, it's true.
Vote Restore Britain!
When PulseChain launched, the one thing I knew we were going to be missing was infrastructure.
Not hype.
Not another token.
Not another chart.
Infrastructure.
Ethereum had years to build out the tooling, RPCs, indexers, data services, dashboards, wallet support, integrations, and all the invisible pieces that make a chain actually usable.
PulseChain needed a lot of that on day one.
So thatโs where I focused.
It is a relatively thankless part of the ecosystem. Most people only notice infrastructure when it breaks. It does not really have a flashy narrative. It does not pump because a node stayed online. It does not trend because a backend service quietly handled traffic for another app.
But a lot of projects depend on it.
That work was hard, and for the most part, I do not really make anything from it. I did it because I thought it needed to be done.
At this point, I consider a lot of that infrastructure work done. Or at least done enough that I can start shifting more attention toward the next missing pieces.
Software is like an onion.
There are layers upon layers.
Most people only see the final app, the interface, the button they click, or the thing they directly use. But underneath that are all the other pieces that have to exist first: RPCs, APIs, data services, indexers, contracts, routing logic, security assumptions, UX standards, integrations, and a dozen other things nobody really wants to think about until something breaks.
Some software cannot properly exist until other software exists beneath it.
And when those lower layers are missing, someone has to build them.
That is a lot of what my work on PulseChain has been. Not just building the thing people see, but building the things the visible thing depends on.
That also means I have had to put my own personal opinions aside in a lot of cases.
There is software out there that I do not personally agree with. There are projects I would not use myself. There are decisions I may not like, products I may not believe in, and approaches I may think are wrong.
But infrastructure has to be agnostic.
If you are building foundational layers for an ecosystem, you cannot only support the things you personally like. You cannot alienate every project you disagree with. You cannot build in a way that says, โThis only works for my corner of the chain.โ
That is not how we grow.
A real ecosystem needs room for different products, different opinions, different strategies, and different types of users. Even when I disagree with someone, that does not automatically mean they should be cut off from the infrastructure layer.
That is not always easy.
But I think it matters.
And to be clear, I see a lot of devs working very hard on a lot of things.
I do not like shitting on people who are actually building good things. I can personally disagree with someoneโs direction and still respect the work they are putting in. Those two things are not mutually exclusive.
There are projects I might not use myself. There are design choices I might not make. There are products I might think should go a different direction.
But if someone is showing up, writing code, solving problems, and trying to make the chain more useful, I respect that.
The beauty of software is that none of this has to be winner-take-all.
If another dev does not like Cappy, but they like a feature in it, they can implement that idea in their own way. If they think I missed something, they can improve on it. If they think my approach is wrong, they can prove it by building something better.
That is how this should work.
And in cases where there is strong overlap, I will even help where I can, as time allows.
That is how you grow.
That is how you get taken seriously as a chain.
In my opinion, anyway. I can be wrong.
That is part of why Iโm building Cappy.
If you do not like Cappy, you do not have to use it. I mean that sincerely. I am not building a wallet because I think everyone has to agree with my taste, my priorities, or my product decisions.
I am building the wallet I personally would want to use.
That may not be the wallet you want to use. Thatโs fine. Some people like Microsoft Word. Some people like Google Docs. Some people like Rabby. Some people like MetaMask. Some people want something simple. Some people want something powerful. Some people want every possible feature. Some people want as little friction as possible.
There is no single perfect answer for everyone.
But the wallet I wanted to use on PulseChain did not exist in the form I wanted it to exist, so I decided to build it.
A lot of the pieces of this chain, I honestly thought other people would eventually figure out. In some cases, they did. In other cases, not really.
I thought we would attract more external devs. I thought more projects would port over. I thought more teams would support their forks. I thought more of the obvious gaps would get filled over time.
Maybe I was wrong to expect that.
Maybe I should have seen it differently from the beginning.
Either way, it is what it is.
At some point, I stopped waiting for other people to build the things I wanted to see exist.
That does not mean I think I am always right. I am not infallible. I am sure I will make decisions some people disagree with. I am sure some people will not like the way I build things. I am sure some people will think I should be working on something else.
That is fine.
You can dislike the software I write and not use it.
It really is that simple.
But I am going to keep building the things I believe are important.
People ask, โWhat about Sigma?โ
I am working on it in parallel with Cappy.
People ask, โWhat about Cross Chain IcosaHedron?โ
I am working on it in parallel with Cappy.
People ask, โWhat about the other ten pieces of software the ecosystem still needs?โ
That is exactly the point.
These things are not always separate in the way people think they are. A wallet needs infrastructure. Cross-chain systems need reliable data. DeFi products need tooling. User-facing apps need lower-level services that most people will never directly touch.
Some things need other things to exist before they can function properly.
And if those other things do not exist, someone has to make them.
I am not randomly jumping between projects.
I am building the layers that make the next layer possible.
I have been told many times that I should run a foundation, or try to organize things, or try to be some kind of public face for the ecosystem. I do not know if I would even be good at that. Maybe I would. Maybe I would not.
What I do know is that I am at least decent at software.
So that is where I am putting my energy.
I can try to do the things I wish more people were doing.
Am I the happiest with Richard right now? No.
Do I respect what he has built? Yes.
Am I still hopeful for the future? Yes.
Those things can all be true at the same time.
I have more or less put everything on the line to move quickly and build things I think matter. The infrastructure phase was the first big priority, and I think that work is now far enough along that I can focus more heavily on actual products people can touch, use, critique, and hopefully benefit from.
Many of you support me, and I see that.
I do not take it lightly.
All I can really promise is this: I am going to keep trying to give this ecosystem the best software I can.
Not because everyone has to use it.
Not because I think I am the answer to every problem.
Not because I agree with every project.
But because I still believe PulseChain deserves better tools, better infrastructure, better user experiences, and more people willing to actually build the missing pieces.
That is what I am trying to do.
Thanks for coming to my Ted Talk. I hope you like the things I do. None of this is any kind of advice, especially financial and P.S. Cappy comes with a block explorer that (hopefully) people find fast and functional enough to like. It was a requirement to make Cappy work. Modified Blockscout fork.
History made. We won ten out of ten seats, with overwhelming majorities in every single one.
Great Yarmouth First, then we Restore Britain.
A very special day.
Today I was fired from Coinbase after 7 years of total dedication to Brian and his team.
My mistake?
Asking why weโre โprotecting usersโ from PulseChain while simultaneously listing every low-liquidity meme coin known to man.
HR sat me down, slid over a 47-page NDA, and politely explained:
โPulseChain doesnโt exist, Richard Heart never existed, and if users discover self-custody we all have to learn how to code again.โ
They made me sign something called a โDecentralization Awareness Suppression Agreement.โ
Apparently itโs very important that nobody finds out you can trade without us.
Anyway, bullish on whatever got me fired. ๐ช