Sabitlenmiş Tweet
The most honest man in crypto. He also launched PulseChain $PLS, PulseX $PLSX, and $HEX.
PulseChain.com
Richard Heart@RichardHeartWin
Hello PulseChain, PulseX, HEX, Bitcoin, Ethereum, and free speech, I won for us all!
English
bretep
3.4K posts
Guys, a well respected $HEX OG sent me this last night and it's kinda freaking me out.
If you look at Richard Heart's twitter profile, his new location is South America.
Do you think this could be real?
English
@LibertySwapFi @chaztownjerky You need to optimize your requests if you’re hitting guards. There is a fine balance between availability and unlimited use. The guards on the FREE rpc are there to protect normal users, not services that should be running their own RPCs.
English
@bretep @chaztownjerky Well, I don’t believe it’s a bug in our code, though I’ll double-check to be sure. Monitoring large batch RPC requests is a basic skill that we do practice. That said, I appreciate your response.
English
So, the problem with PulseChain RPC sources was caused by someone DDoSing the public RPCs, preventing them from responding properly. Crazy 🤪
Liberty Swap ⚡️ Bridge2Pulse™️ Zero-Fee DEX@LibertySwapFi
LibertySwap has just built a component called Batched RPCs. It combines our private RPC with all publicly available PulseChain RPC endpoints. Every 5–10 minutes, we ping these RPCs and route orders through the most stable one. This should help our protocol orders achieve better execution going forward. Hopefully it improves the overall reliability for users.
English
@LibertySwapFi @chaztownjerky You’ve got a bug in your code/monitoring then. This is inaccurate information. Extensive external monitoring and internal show we serve no stale blocks. Zero RPC calls would be routed to anything not at head. 😂
English
Thank you for confirming that the main RPC for PulseChain has not been affected by a DDoS attack. We truly appreciate the clarification.
That said, we have been observing some block lag on rpc.pulsechain.com. For example:
•Latest block on chain: 18,523,900
•rpc.pulsechain.com: 18,523,860
A delay of around 10–40 blocks can occasionally lead to incorrect swap price quotes or inaccurate swap simulations.
We are doing our best to further investigate the situation on our side and understand the root cause. If you have any insights or guidance regarding the behavior of the main RPC, we would greatly appreciate learning from your experience 🙏
English
Nice work!
dreaded@dreaded_369
#PulseChain is now the chain with the 2nd highest number of verified contracts on @SourcifyEth - whereas not long ago we weren't top 10 - all thanks to @RenatoPulse and myself. We aim to improve security, transparency and user experience on the block explorers. @RichardHeartWin
English
Age verification is the stupidest thing in technology.
A. You teach underaged people to lie and not feel any guilt.
B. If you require identification, you are violating the privacy of everyone in the world. Person A authorized to use computer X, and you claim a virus did…
Absolutely zero good comes from stupid laws like this. How about we teach kids and adults good morals and values, let them make choices, you know, learn to become an adult, a good human citizen that enjoys human rights such as privacy and speech. The world would be a better place if we all did that.
English
bretep retweetledi
Hope you're all safe out there in this wild world.
English
bretep retweetledi
bretep retweetledi
It's vital that you go to ProveX.info and inspect the leaderboard. A random check discovered an XRP address that was credited more than it should have been. And if a random check finds an error, there's likely more errors.
If you don't verify that every single sac is legit and credited right, then fairness is less likely to exist upon the tokens launch. I think there's only 7500 to check, and checking is more important towards at the top of the leaderboard than the bottom, value wise. Probably the place where the most errors might be found are in the non EVM things.
Or you could also not inspect, but fairness is cool and worth working for. If you don't want to post what you find here, there's a 1:1 simplex chat link on app.provex.com if you click the question mark.
English
> be nerds
> look into persona (used by discord)
> kyc (know your customer) service
> used for age verification
> search on internet (shodan)
> find weird server
> image 1
> openai-watchlistdb.withpersona
> openai-watchlistdb-testing.withpersona
> lolwtf
> look inside
> supposed to be behind cloudflare to hide ip
> openai messed up
> not behind cloudflare
> real ip shown
> using google cloud
> lookup cert history
> 2023-11-16 created
> 2024-02-28 gets cert
> 2024-03-04 prod goes live
> google stuff
> openai and persona partners
> partner around timeline of certs
> back to searching stuff
> find withpersona-gov
> look inside
> okta (image 2)
> lolwtf
> look inside
> website accidentally leaking stuff
> fedramp-private-backend-api
> look inside
> api .js accidentally exposed
> look inside
> wtf "SARInstructionsCard"
> wtf "app.onyx.withpersona-gov"
> wtf "FINTRAC"
> wtf "PrivatePartnershipProjectNameCodes"
> image 3
> wtf "AsyncSelfie"
> look inside
> openai, persona, send data to us gov
> feds map face to financial records
> map face using AI
> map face to ICE stuff
> api stores data for lots of stuff
> image 4
tl;dr persona kyc and openai are frens, using your selfie for verification and sending to ICE (or USGOV in general), using AI to tie to your financial records. see subsequent post for full write-up. its long and not mobile friendly
English
bretep retweetledi
I'm not a fan of violating people's freedom of association or speech. Which they're doing for some people not as old as you. Especially when it's a back door to remove all anonymous speech. Because people can't control their teens, I can't view speech on websites without doxxing myself? No thanks.
English
bretep retweetledi
bretep retweetledi
People have been to literal jail IRL to bring you zero knowledge proof based privacy on Ethereum, and the anonymity set is huge, but almost no one talks about it. If you think Privacy is the future, no one is doing it as well as Ethereum, absolutely no one. For years!
ZEC and XMR bros, you're gimped by having to suck middleman D to trade out, but on ETH you can stay all on chain. No surprise middleman theft crap, just smart contact risk, which is the least risk you can hope for in finance.
English
Yeah, it’s totally doable. If law enforcement isn’t tapping radio engineers for this by now, they’re sleeping on the tech stack. Drones would crush it for sweeping vast areas—pair ‘em with SDRs and high-gain antennas to sniff out that BLE signal.
Dave Kennedy@HackingDave
For the Nancy Guthrie case, an idea and maybe a crazy one but she had a pacemaker which often implantable devices use bluetooth such as Medtronic's. Couldn't you war-drive (drones even better) with a high gain antenna with amplifiers - get the MAC address from the provider, and comb the city and locations looking for that specific mac? I'm also sure if you had cooperation with the manufacturer they may provide the protocol, law enforcement could use a custom interrogator to "ping" the device and elicit a response. Pacemakers last months or years. It would continue to transmit even if (God forbid) someone was deceased. High gain + LNA + good SDR - 500+ ft possible with class 2 transmitters (normally in bluetooth pacemakers - common in implants, ~10 mW output) Parabolic + high sensitivity gear - 1000+ ft in ideal RF conditions Not saying this range is possible, with BLE + body interference + 2.4ghz being a heavily used spectrum = much lower range. Previous research has tested insulin pumps upward of 300+ ft in the past in BLE. Companies that use bluetooth in pacemakers: Medtronic Abbott Laboratories Boston Scientific Now in stating that - there's a bunch of limitations here - broadcast timing. They all use low power bluetooth, but if they have access to Nancy's phone and paired - would there be a way to take that pairing connection, amplify it and run it through? You could potentially extract pairing keys/secrets and emulate the phone's connection with an amplified setup (e.g., SDR spoofing the phone's BLE master role). A lot of "ifs" here just wondering if it's technically possible based on what I know these conditions would need to be true: The implant uses RF telemetry that can transmit without an external programmer actively interrogating it. The device is configured to advertise or beacon. The identifier is detectable passively. The identifier is not randomized. The device is currently transmitting. You are within viable range (which is likely very short). The RF environment is not swamping it. If solely using MICS frequencies this wouldn't work (402-405mhz): Very low power Designed for short-range use Often magnet-activated or programmer-initiated Session-based communication Encrypted/authenticated in modern systems The 2.4 GHz band is crowded; distinguishing one pacemaker from thousands of BLE devices in a city like Tucson would require a lot of noise reduction/filtering, but technically I think it's possible. Also note that law enforcement did state that the phone disconnected from the pacemaker - hinting at bluetooth was actually enabled. Papers used for analyzing this as a viable option: mdpi.com/1424-8220/20/1… mdpi.com/1424-8220/23/7… mdpi.com/1996-1073/13/4… pmc.ncbi.nlm.nih.gov/articles/PMC28… pmc.ncbi.nlm.nih.gov/articles/PMC10… digitalcommons.calpoly.edu/cgi/viewconten… secure-medicine.org/hubfs/Archimed… sciencedirect.com/science/articl… medtronic.com/en-us/e/produc… armis.com/research/bleed… thinkmind.org/articles/cyber…
English
@CryptoCyberia Actually, I disagree. I believe it has a good chance. I’ve detailed some of it in this post and another one.
x.com/bretep/status/…
bretep@bretep
The future of software isn’t code. It’s intent. As agentic AI matures, everything between “what you want” and “physical hardware doing it” becomes an optimization problem AI solves end-to-end. What disappears: → Programming languages (AI invents its own) → Compilers, as we know them → Operating systems as a human concern → ISAs designed for human-written code → “Software engineer” as a career What remains: → Humans defining what they want and why → Hardware fabrication — atoms still take time → Materials, energy, and physics → Trust and verification The engineer of the future isn’t writing code. They’re either articulating intent with precision or manufacturing the physical systems AI designs. The uncomfortable question: security. If AI designs every layer from spec to silicon, attackers will use AI too. The battlefield shifts from exploiting human-written bugs to adversarial AI trying to corrupt the spec-to-hardware pipeline itself. Poisoning training data. Manipulating specs. Injecting flaws at the fabrication level. Defense becomes AI-vs-AI verification — multiple independent systems auditing each other, grounded in mathematics simple enough for humans to still trust the foundation. The last human job in the stack isn’t writing. It isn’t coding. It’s deciding what matters — and verifying that what was built actually serves that purpose. The constraint was never intelligence. It was always atoms and energy.
English
If you believe that there is even a one in a million chance of this happening this year, you're brainwashed by grifters and in one of the gayest cults I have ever seen.
Natural language to binary compositor is either impossible totally, or an extremely difficult task.
Get real
X Freeze@XFreeze
Elon Musk predicts that AI will bypass coding entirely by the end of 2026 - just creates the binary directly AI can create a much more efficient binary than can be done by any compiler So just say, "Create optimized binary for this particular outcome," and you actually bypass even traditional coding Current: Code → Compiler → Binary → Execute Future: Prompt → AI-generated Binary → Execute Grok Code is going to be state-of-the-art in 2–3 months Software development is about to fundamentally change
English