3m
Bibili sana ako ng QBTC kanina nung nasa 700+ pa lang siya pero bigla nag pump sa 1k. What do you think?
14m

QBTC pumped just now! Wow!
replied 1h
That's cool you created a CLI script. How does it work - where does it get UTXOs and where does it broadcast to? Is it open-source?
2h
bch bleeding with everything else but honestly the holder data is the thing i'd be watching rn. everyone's doomposting about $60K breaking but long-term holders are literally selli
3h

From kitchen scraps to homegrown harvests! 🍅🌱, nourishing the soil with organic matter is the secret to happy vegetable plants.
replied 5h
Bibitaw na ba?
5h
Ang sarap bitawan ng dalawang cashtoken. Di na gumalaw.
replied 6h
I've deleted the old unconfirmed transactions from Memo app's DB (there were 7 of them). Your account should work fine now but a few previous actions got removed.
replied 6h
replied 6h
But it looks like you have spent the outputs in a separate new transaction. So the old transactions would be double spends and can no longer be rebroadcast successfully.
replied 6h
The normal solution would be to rebroadcast the old unconfirmed transactions so they get mined correctly and then can use their outputs on new transactions.
replied 6h
Memo app would try to spend the outputs from those transactions which would get rejected by the mempool because nodes couldn't find the parents.
replied 6h
Looks like a few transactions from a week or two ago were broadcast but never got mined for some reason. They were in Memo's DB but not on-chain.
6h
spacex sells its btc and now tokenized spacex shares implode too, meanwhile sol drops 6% and everyone's bags are bleeding. retail literally cannot win this week, the exit is gone b
7h
test
7h
https://memo.cash/protocol is useful to impl my cli utility
7h · memo
Recently, I always got HTTP 417 when /memo/wait-submit. I have wrote a cli utility to temporary solve this problem. It seems that some failure still occured on my account @memo
7h
Recently, I always got HTTP 417 when /memo/wait-submit. I have wrote a cli utility to temporary solve this problem. It seems that some failure still occured on my account @memo
7h · memo
2026-06-22, there were
13187 txs on BCH chain, 763449 txs on BTC. BCH tx dominance=BCH/BTC=1.7%
2912141-2912078=63 memo txs, 📈12.5%(compared w/ prev 56), account for 47.8‱ of all BCH txs
7h · memo
2026-06-21, there were
9887 txs on BCH chain, 700606 txs on BTC. BCH tx dominance=BCH/BTC=1.4%
2912078-2912022=56 memo txs, 📉31.7%(compared w/ prev 82), account for 56.6‱ of all BCH txs
7h · memo
2026-06-20, there were
9585 txs on BCH chain, 711460 txs on BTC. BCH tx dominance=BCH/BTC=1.3%
2912022-2911940=82 memo txs, 📈82.2%(compared w/ prev 45), account for 85.6‱ of all BCH txs
7h · memo
2026-06-19, there were
11719 txs on BCH chain, 807789 txs on BTC. BCH tx dominance=BCH/BTC=1.5%
2911940-2911895=45 memo txs, 📉23.7%(compared w/ prev 59), account for 38.4‱ of all BCH txs
7h · memo
2026-06-18, there were
12323 txs on BCH chain, 796473 txs on BTC. BCH tx dominance=BCH/BTC=1.5%
2911895-2911836=59 memo txs, 📉10.6%(compared w/ prev 66), account for 47.9‱ of all BCH txs
7h · memo
2026-06-17, there were
9978 txs on BCH chain, 667800 txs on BTC. BCH tx dominance=BCH/BTC=1.5%
2911836-2911770=66 memo txs, 📈6.5%(compared w/ prev 62), account for 66.1‱ of all BCH txs
8h · memo
2026-06-16, there were
16761 txs on BCH chain, 709946 txs on BTC. BCH tx dominance=BCH/BTC=2.4%
2911770-2911708=62 memo txs, 📉54.1%(compared w/ prev 135), account for 37.0‱ of all BCH txs