crypto newb, 💩 shitposts are my own
Joined April 2019
- Tweets12K
- Following2.2K
- Followers272
- Likes5.6K
Pinned Tweet
Cause nobody got rich eating fancy apples. Meme coins get you that shot. It’s a lottery with better odds.
bitcoinearly retweeted
Here's 4 steps to run an uncensored AI on your own GPU for $0:
I run a local abliterated Gemma 4 for anything I don't want leaving my machine
By the end, you'll know how to:
- run a model which has no refuses
- plug it into Claude Code
- do it all for $0, no API key, no account
So, let's go step by step:
1. Install Ollama
curl -fsSL ollama.com/install.sh | sh
you want a recent version, older builds don't speak the Anthropic API and don't support Gemma 4
2. Pull the model
ollama pull igorls/gemma-4-12B-it-heretic-GGUF
the biggest mistake people make here is grabbing a random "uncensored" tag with no quality numbers
this one is abliterated with Heretic. refusals went 99/100 → 0/100 at a KL divergence of 0.028 from the original, so you keep almost all of the base model's capability
one thing: it's still Google's Gemma license underneath, fine for personal use, but read the terms before you build a product on it
3. Turn off thinking (the part every other guide skips)
Gemma 4 is a hybrid thinking model and the abliteration targets non-thinking mode
leave thinking on and the reasoning block eats your token budget and the answer gets cut off
ollama run igorls/gemma-4-12B-it-heretic-GGUF
/set nothink
if you're calling the API instead, add "think": false to the request
4. Plug it into Claude Code (OPTIONAL)
ollama launch claude --model igorls/gemma-4-12B-it-heretic-GGUF
or manually:
export ANTHROPIC_BASE_URL=http://localhost:11434
export ANTHROPIC_AUTH_TOKEN=ollama
claude --model igorls/gemma-4-12B-it-heretic-GGUF
two gotchas:
- bump the context first. Ollama defaults to 4k and Claude Code's system prompt alone is bigger than that, so the model never sees its tool instructions. restart the server with OLLAMA_CONTEXT_LENGTH=32768 ollama serve (setting it in your shell does nothing if Ollama is already running as a service). this needs more VRAM than the 8GB below
- Gemma 4 tool calling is still rough, you should expect some failed edits, imo for serious agentic work use qwen3.5 or glm-4.7-flash instead
What you need:
- 8-12GB VRAM for Q4 (12B)
- ~8GB of disk for Q4, ~13GB for Q8
- more of both if you want a big context
honest take:
- "abliterated" means refusals removed, not quality added. it's still a 12B
- fewer refusals ≠ smarter. for real coding work I still use cloud models
- you own the weights, your prompts never leave the box. that's the actual win
*IMPORTANT: don't use it for anything illegal or harmful. that's on you, not the model
now i'm collecting a list of every uncensored model i'm adding to my local stack and which tasks each one replaces for me
also planning a big "Uncensored 101" article, still figuring out all the angles
save it so you don't lose it
bitcoinearly retweeted
Fan gets ejected for passing the ball back to the female referee
Luka Doncic: “What the f*ck are you doing?”
bitcoinearly retweeted
JUST IN: @Hyperbeat card volume hit a record $77,755 yesterday.
Two payments made up more than half of this, but the remainder alone would still have been Hyperbeat's fifth best day since launching in January.
bitcoinearly retweeted
🚨 BREAKING NEWS: Gmail Users Need to Pay Attention!
If you have a Gmail account, this is something you need to know.
Google’s AI features have raised serious privacy concerns about users’ personal emails, attachments, bank statements, tax documents, and medical information.
These concerns are now at the center of a class-action lawsuit.
Here are 5 steps to protect your Gmail privacy:
bitcoinearly retweeted
crypto never stops evolving, and neither should the platforms leading it.
security, transparency, and user confidence must remain the priority.
bitcoinearly retweeted
I want to thank our users for their patience and support as we continue working through this recovery process.
We've completed the latest Proof of Reserves verification, giving users another way to independently check that their assets are backed.
There's still work to do, and we'll continue to communicate our progress openly.
bitcoinearly retweeted
We've known the Cardinal crew since their Kwenta days, so it’s great to be building together again.
Their Yield Perps product uses our options to hedge LP exposure and price positions. This gives traders leveraged exposure to yield whilst maintaining a familiar perps experience.
There's a lot to explore with options, and this is the kind of product that will capture market share as the pie grows.
Every few years, a new derivative goes from obscure to essential.
We think Yield Perps are next, and the foundation matters. We built them on @DeriveXYZ for the liquidity to scale and the markets to expand.
📜: blog.cardinal.trading/why-we…
Like with so many things nowadays, people believe the dumbest lies but need endless proof to believe the obvious.
Binance
@cz_binance
bitcoinearly retweeted
Latest Withdrawal Update
Withdrawals have now been re-enabled for the following networks and assets:
New:
✅ SOL: SOL, USDT, USDC
Already Enabled:
✅ BTC: BTC
✅ ETH: ETH, USDT, USDC
✅ BSC: BNB, USDT, USDC
✅ XRP: XRP
✅ Base: ETH, USDC
✅ DOGE: DOGE
✅ OP (Optimism): ETH, USDT, USDC
✅ ARBITRUM: ARB, ETH, USDT, USDC
✅ TRX: TRX, USDT
We will continue to restore additional assets and networks in phases as security checks are completed. Further updates will be shared through official Binance channels.
Latest Withdrawal Update
Withdrawals have now been re-enabled for the following networks and assets:
New:
✅ ARBITRUM: ARB, ETH, USDT, USDC
✅ TRX: TRX, USDT
Already Enabled:
✅ BTC: BTC
✅ ETH: ETH, USDT, USDC
✅ BSC: BNB, USDT, USDC
✅ XRP: XRP
✅ Base: ETH, USDC
✅ DOGE: DOGE
✅ OP (Optimism): ETH, USDT, USDC
We will continue to restore additional assets and networks in phases as security checks are completed. Further updates will be shared through official Binance channels.
bitcoinearly retweeted
You're confident your wife has thought about him more than once, in what manner? who can say
Bookmark and follow these steps.
How to avoid getting hacked and losing your money
- Remove any extensions, dependencies, and approvals you don't need. Especially with AI, everyone is installing dependencies they don't understand but these are hidden attack vectors.
- If you do have dependencies avoid auto updates as soon as they come out. If a major repo gets high jacked, people are usually pretty good at spotting and sharing on socials.
- Never store funds you aren't willing to lose on hot wallets. Period.
- For shipping sensitive things like cold wallets, PO boxes are an option so you don't expose your personal details.
- Always double check links to make sure its the right domain. Same practice when sending to wallet addresses.
- Even legit domains can get hijacked these days. If anything seems off about a site don't use it and monitor socials to see if anything is wrong.
- Never use 2FA through text message. Yubikey or Authenticators only. It's also worth looking into whether you can lock down impersonators from your phone number. Some carriers have additional protections you can set up now.
- With DeFi, something to keep on the back of your head is whether you are willing to lose the money you have here and what is the likelihood that they can cover losses in the worst case scenario. (Same with exchanges)
- Be careful with virtual meetings with strangers online. If you need to avoid Zoom at all costs. I tend to use G Meet only.
- Even with people you know and trust, there is always still a chance that their accounts could be hacked. The best way to get around this is to have a device for work and a device for sensitive stuff.
- Antiviruses are a given. They aren't perfect but they do help with the obvious stuff.
- Likewise you can also ask your LLMs to scan your devices, ports, and see if anything looks off.
- Be very careful with API keys on important accounts. If you don't need write access don't provide these permissions. Make sure to clean these up regularly if you don't need them.
- On socials the first thing I do with cold DMs is check for mutuals. It's not perfect but it's a good initial filter. Even then don't touch any downloads or weird links.
- Backup codes should never be stored online. If it was ever online consider it compromised.
- Never buy important things from a reseller. If you can get it directly from the official source.
- Never leave important personal devices outside in the public unwatched.
I think a lot of people tend to overthink security and get paranoid about it but
bitcoinearly retweeted
Binance has allocated US$6.34 billion of its own corporate funds to the User Fund. In the current User Fund, BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC have all achieved 100% full reserve backing. We will continue to purchase other altcoin assets that are not yet 100% matched through market and over-the-counter (OTC) channels until the replenishment ratio for all tokens reaches 100%.
We completed a new Proof of Reserves snapshot at 08:00 (UTC+8) on October 31, 2026, and have updated it on the Proof of Reserves website. This snapshot presents the latest fully verified asset position and is part of our ongoing commitment to transparency. Because generating zero-knowledge proofs requires substantial computing resources, it is expected to take approximately 40 to 50 hours. If you hold any of the aforementioned ten tokens, you can independently verify, once the complete proof is generated, that your assets are backed by at least 1:1 full reserves. The complete proof is expected to be published on Tuesday, November 3, 2026 (UTC).
bitcoinearly retweeted
⚠️How can you tell a DNS is Hijacked when you visit an official website?..⚠️
At least 12+ domains got hijacked last night, serving wallet drainer code on their official website.. All but 5 have now moved their DNS to Vercel/Cloudflare to mitigate and those 5 are still compromised, DO NOT VISIT!
The URL can be 100% correct, but the website you're visiting can still be malicious.
This compromise did not break anything from the teams flow, setup, compromise anything they did, it appears someone inside name(.)com (The registrar) change the nameservers to the domains. If you use them as a registrar I would consider moving away and at minimum setup cloudflare for hosting/filtering.
If you are a user, there really isn't a way to detect this unless you are checking WhoIs, DNS updates, ASN numbers, and many more which most don't. The only way to tell is that when you go to the website it will ask for your seed phrase/private key, or prompt you to sign an odd transaction. The transaction part is tough to spot which is why I recommend always using @RevokeCash extension to help spot this for you with the transaction simulator...
If you are a business and not using cloudflare, let's talk, this is basic proper security on domains outside of domain lock, etc. You have to be prepared ahead of time to prevent/mitigate this in an instance moment!
Stay Safe & Stay Vigilant
