1.2.9:0

What's Changed

BitcoinTX 1.2.9 is the stable version of BitcoinTX 1.x (below, "About this release"). It fixes the bugs found in 1.2.8's testing and the reviews since, several of which could make a tax figure wrong; lets an install that uses Tor download the price history once without it, if you agree; asks before Delete All wipes the ledger; and runs BitcoinTX as its own user instead of root. Updating from 1.2.7, you also get 1.2.8's changes, marked (1.2.8): prices at the hour, one price choice, inherited bitcoin and consolidation fees.

What to do after updating

• Reload BitcoinTX's page in your browser. A page still open from the version before can show a date originally acquired or a date of death a day early, and save that day with an edit.
• Ledger Review, then Recalculate Ledger. A task asks once. First open Settings > Ledger Review in BitcoinTX: "Figures that Recalculate Ledger would change" lists each transaction whose figures move, old and new; most move by a cent or two. Then run the StartOS action Recalculate Ledger, or Settings > Recalculate Ledger in BitcoinTX.
• Check your tax timezone in Settings > Tax Timezone (below, "Your tax timezone").
• Update your AI connector. In your AI app's configuration, change the version after btctx-mcp== to 1.2.9 and restart the AI app.
• Updating from 1.2.7 or earlier? Also log in again (everyone does once), and confirm where prices come from: unless the action Price Source & Privacy sets it, BitcoinTX's Dashboard asks once, and asks nobody until you do; if you never made a choice in that action, a task asks once.

Fixes that change tax figures

Each says who could be affected and what to do. Unless it says otherwise, any tax year with such a transaction can be affected. Most ledgers need only the steps above.

• Cost basis to the cent. A lot sold, spent or moved in pieces could claim a few cents more or less than it cost, and a disposal's last row could come out below $0. Versions 0.8.0 to 1.2.8, any tax year; cents only. What to do: Recalculate Ledger, as above.
• A spend's network fee counted twice in its gain (1.2.8). With a BTC network fee, a Spent withdrawal's gain was too high by the fee's value, usually a few dollars. Versions 0.9.2 to 1.2.7, every tax year; only ever more tax, never less. What to do: Recalculate Ledger, as above. Whether to amend a filed return over a few dollars is for you or your tax professional to decide.
• Old ledgers, started before 0.9.2. A bitcoin withdrawal of a purpose BitcoinTX doesn't list (such as "Expenses"), or of none, now counts as Spent, at what was saved as received; it counted as a sale, at $0 when that amount was kept only in an older field, or with its network fee not taken off. A purpose or source saved with spaces (" gift ", " Income ") now counts as the one it names: such a gift counted as a sale, such income was left out. Versions 0.9.2 to 1.2.8 (a purpose or source with spaces: every version to 1.2.8). What to do: Ledger Review lists those withdrawals: confirm Spent or choose Gift, Donation or Lost, then Recalculate Ledger. One listed as "none recorded" may have lost its amount at a recalculation under 1.2.8: the copy of the database BitcoinTX made before updating to 1.2.8 still holds it (the changelog says where).
• A date originally acquired or a date of death stays the date you entered. After a change of the tax timezone by about 12 hours or more, it could move a day, changing a holding period or an inheritance's value. Versions 1.2.6 to 1.2.8. The update keeps each date as the form showed it. What to do: if you changed the tax timezone by many hours after entering such a date, check those dates against your records.
• Your tax timezone. While none had been chosen, a login saved the browser's timezone as the tax timezone and recalculated the ledger, without a word: a sale near midnight or near its one-year anniversary could move to another tax year or term. Versions 0.8.0 to 1.2.8. Now a login sets it only on an empty ledger. What to do: check Settings > Tax Timezone. If it's where you file, today's figures are right, and if a return you filed differs from them, ask your tax preparer whether to amend it. If it isn't, choose the right one there.
• Imports: a decimal comma or a stray comma. The CSV and River imports read "0,5" BTC as 5 BTC and "21.000,00" dollars as $21; a CSV row with a comma outside quotes (an amount like 20,000.00) moved every later column, so a $20,000 basis was saved as $20. Every version with the imports; both are now refused. What to do: if a file you imported had such a number, compare its transactions with the file and edit any that differ.
• River: auto-withdrawals and mining payouts. An auto-withdrawal to your wallet was suggested as a spend (a sale on Form 8949), and a mining payout was skipped (its income left out). Versions 0.7.0 to 1.2.8. What to do: if you kept them as suggested, delete those spends and import the River file again: it suggests Transfers to Wallet, and the payouts as income.
• A transaction of the same amount skipped as already recorded. The River import and the AI connector left out a transaction when another of the same amount was recorded within 48 hours (two Interest payouts a day apart), or, for the AI connector, into or out of the other bitcoin or dollar account: its income or cost basis was missing. Versions 0.7.0 to 1.2.8. Now only a true duplicate (the same kind, amount and minute) is left out, unless you say otherwise. What to do: check that transactions of the same amount within two days of each other are all in your ledger; previewing a River file again shows any it skipped.
• The same rows saved twice. An AI connector add sent again after a timeout, or a file imported in two tabs at once, could save its rows twice. Every version. What to do: look in Transactions for a transaction recorded twice, side by side, and delete the extra copy.
• A gift made a Spent later. A gift, donation or lost coins saved in the form, then made a Spent through the AI connector or the API, was a $0 sale, its whole cost basis a loss. Versions 0.8.0 to 1.2.8. What to do: Ledger Review lists it under "Spent withdrawals saved with $0 proceeds": clear its proceeds (it's then valued from the price) or type what you received. Made a Sell that way, it's a $0 sale Ledger Review doesn't list: look in Transactions for a Sell with no proceeds and enter what you received.
• A sale edited to $0. Setting a sale's gross proceeds to 0 kept its old proceeds and gain. Versions 0.8.0 to 1.2.8. What to do: if you did that and it came back with its old figure, set it to 0 again.
• A Buy, or bitcoin, with no cost. Through the API or the AI connector, a Buy could be saved without its cost basis, and a dollar deposit moved into Wallet or Exchange BTC kept its dollar figure (often $0) as the coins' cost: their later sale was all gain. Versions 0.8.0 to 1.2.8. What to do: Ledger Review lists "Buys with a $0 or blank cost basis" and "BTC deposits (not income or a rebate) with a $0 or blank cost basis": enter what each cost. Ledger Review doesn't list one moved with another dollar figure: if you moved a dollar deposit into Wallet or Exchange BTC through the AI connector or a program of yours, check its cost basis.
• A sale edited through the API with blank proceeds was saved as a $0 sale, and one with proceeds below its fee was kept. Versions up to 1.2.8; only programs of your own, never the app or the AI connector. What to do: compare such sales with your exchange's records.
• Ledgers from before 0.8.0. An old Spent opened in the edit form with proceeds of $0, so a save made it a $0 sale; an old Sell opened with gross proceeds of $0, and typing its net there took the fee off a second time; an old withdrawal changed into a Sell through the AI connector or the API got proceeds too high by its fee. Versions 0.8.0 to 1.2.8, only before any recalculation. What to do: if you saved one so, Ledger Review lists a $0 spend; open an old sale you edited, or an old withdrawal you made a Sell, and check that its Gross Proceeds (USD) is what it brought before the fee.
• Applying the hour's prices during an edit. A transaction edited while Ledger Review applied the hour's prices could get the value worked out for its old amount or hour. Version 1.2.8 only. What to do: only if you did that, open it and clear its value to price it again.
• A dollar withdrawal listed as a gift of bitcoin in the Complete Tax Report, when a bitcoin purpose was left in the form. Every version; never on Form 8949. Nothing to do.
• Your own Mempool's address changed during a price lookup. For 10 minutes, the old Mempool's prices could be used and stored. Version 1.2.8 only. What to do: only if you changed it because its prices looked wrong, check the values priced from your Mempool since then.
• A price under one cent stored as $0 (1.2.8). Versions 0.9.2 to 1.2.7; no such price is known. What to do: if you ever saw a value "From the price" at $0.00, type it.
• Inherited bitcoin (1.2.8). Recorded as My BTC or Gift, as earlier versions offered, it could print wrong figures: a sale within a year of the death short-term, or a Gift's basis the person's own cost. Versions before 1.2.8. What to do: edit each such deposit to the Source Inherited, with the date of death and its value that day. A deposit saved before 1.1.0 with the source "inherited" follows the rules from the next recalculation; Ledger Review lists any without a date of death.
• Four fixes to this version's new duplicate rules for the AI connector affected no released version: nothing to do.

Privacy (fixed)

• A price choice made without asking (1.2.8; versions 1.2.0 to 1.2.7). Switching Price Source & Privacy to Decide in BitcoinTX instead, or running Set Login Credentials or a hand-run command while it was set, could save Public price sites as your choice in t...

1.2.8:0

What's Changed

BitcoinTX 1.2.8 values bitcoin at the hour of each transaction, makes where prices come from one clear choice, adds inherited bitcoin and consolidation fees, stops a spend's network fee from counting twice, and brings the fixes of a security review.

What to do after updating

• Recalculate Ledger. A task asks for it until you run it. First open Settings > Ledger Review in BitcoinTX: it lists each spend whose figures change, old and new. Then run the StartOS action Recalculate Ledger, or Settings > Recalculate Ledger in BitcoinTX.
• Confirm where prices come from. Unless the action Price Source & Privacy sets it, BitcoinTX's Dashboard asks once to confirm your price choice, and asks nobody until you do. If you never made a choice in that action, a task asks once.
• Log in again. After this update everyone logs in once more.
• Update your AI connector. In your AI app's configuration, change the version after btctx-mcp== to 1.2.8 and restart the AI app. It now lists a sale's or spend's gross proceeds beside the after-fee figure; an older connector could take the fee off twice when it edited one.

Fixes that change tax figures

• A spend's network fee counted twice in its gain. When you spent bitcoin (a Withdrawal, purpose Spent) with a BTC network fee, the fee was counted as its own disposal but not taken off the spend's proceeds, so the gain came out too high by the fee's value, usually a few dollars. Versions 0.9.2 to 1.2.7, every tax year; it only ever showed more tax, never less. What to do: Ledger Review, then Recalculate Ledger, as above. Whether to amend a filed return over a few dollars is for you or your tax professional to decide.

• Inherited bitcoin. Recorded as My BTC or Gift, as earlier versions offered, it could print wrong figures: a sale within a year of the death came out short-term, or a Gift's basis was the person's own cost. All earlier versions, every tax year with such a sale. What to do: edit each such deposit to the new Source Inherited, with the date of death and its value that day. A deposit saved before 1.1.0 with the source "inherited" follows the rules from the next recalculation; Ledger Review lists any without a date of death.

• A price under one cent was stored as $0. A day's price a site gave under one cent was kept as $0.00, and a value filled in from it was $0. Versions 0.9.2 to 1.2.7, any tax year; no such price is known. What to do: nothing, unless you ever saw a value "From the price" at $0.00: type that value (a day already stored at $0.00 stays).

Privacy: a price choice made without asking (fixed)

• Who could be affected: in 1.2.0 to 1.2.7, owners who switched Price Source & Privacy to Decide in BitcoinTX instead (called Choose in BitcoinTX before) after it had been set to Off, Public price sites or My Mempool, or who ran Set Login Credentials or a hand-run command while it was set, if BitcoinTX had stored prices meanwhile. It could then save Public price sites as your choice in the app without asking, and use it after a switch.
• What could have been sent: requests from your server's address to public sites for Bitcoin's price (CoinGecko, Kraken, Bitstamp or Coinbase) and the block height (Blockchain.info, Blockstream or mempool.space). Never dates, amounts or anything from your ledger. The action's Tor setting no longer applied after the switch: only a proxy set in BitcoinTX's own Settings hid your address.
• What to do: confirm or change the choice when BitcoinTX asks once after this update (above), or check Settings > Privacy & Network.

New

• Prices at the hour. Values BitcoinTX fills in from the BTC price (a blank income or rebate value, a Spent's proceeds, a network fee's value) now use the price when the transaction's hour began: the IRS values bitcoin at the date and time. When your choice allows public price sites, BitcoinTX downloads Bitstamp's hourly prices from 2013 once (about 3 MB), each year checked against a fingerprint that comes with this version. Nothing already saved changes: Ledger Review lists, by tax year, values priced at the day that the hour would change, and changes only the ones you apply.
• One price choice. Price Source & Privacy now offers My Mempool on this server, Public price sites, Nobody, or Decide in BitcoinTX instead, with Use Tor and, for Mempool, a backup of public price sites. A new install asks before it starts. In the app, one price card says where prices come from and when the last one arrived, and the Dashboard, the sidebar and the transaction form say which price a value used. Coinbase and CoinGecko are no longer asked.
• Inherited bitcoin. A new deposit source, Inherited: its cost basis is its value on the date of death, and every sale of those coins is long-term, marked INHERITED on Form 8949.
• Consolidations. A transfer within the same wallet (or between exchanges BitcoinTX counts as one) records only its network fee, a disposal of your oldest coins.
• Trust this server. With Decide in BitcoinTX instead, a Mempool on another home server at its https address can be trusted from the price card.

Known limitation

• Through Tor, Bitstamp currently refuses BitcoinTX's requests: the hourly history and past prices don't download; only the live price works. Choose Public price sites without Tor to download them (once checked, the hourly history stays), use your own Mempool for newer values, or type them. Nothing is sent without Tor instead, and no value becomes $0. A fix is planned.

Security and smaller fixes

• From a security review: logging out ends that session for every copy of its cookie (if the database is busy at that moment, a copy lasts until it expires); other people's failed logins no longer slow down a browser that has logged in before; a restore brings back a backup's data and keeps this install's login, AI key and price settings, or changes nothing; every request has limits on size and time; an edit or deletion by the AI connector keeps a backup copy first, and its imports are kept short. The details are published once this version is available.
• Restarting BitcoinTX while it is still starting stops every process of the previous run (from Start9's 1.2.7:1).
• An edit can no longer save a negative fee value.

Everything in 1.2.8

SHA256 Hashes

e301345cf4f73fb4748f91f238cf9a1ccf68c42eae02518914942c6b767f9eda  btctx_aarch64.s9pk
2d984f4efe7fc83bcaf03ec4c38174e7358137f213d4f2f99047b28ab172ba83  btctx_x86_64.s9pk

1.2.7:0

What's Changed

BitcoinTX 1.2.7 adds a Rebates line to the Dashboard and makes a Ledger Review list clearer. It also includes 1.2.6, which fixes what testing the 2026 forms turned up and says plainly who BitcoinTX is for.

New in 1.2.7

• The Dashboard's Income & Fees card shows Rebates (received), in dollars and bitcoin, under Gifts (received). Like gifts, rebates aren't counted as income.
• Ledger Review shows My BTC and Gift deposits without a date originally acquired as a reminder, not an error: after the checks, explained once for the whole group, with the list folded behind Show. Real My BTC deposits (coins you already owned) stay My BTC. Only if some were really card sats-back saved as My BTC, change those to Rebate and check that the cost basis is their value on the day received (clear it to use that day's price).

Update your AI connector too

• Using an AI assistant with BitcoinTX? In your AI app's configuration, change the version after btctx-mcp== to 1.2.7 (Connect an AI Assistant shows it) and restart the AI app. Your AI key stays the same. Until you do, every reply says so, and a connector older than 1.2.6 keeps its old guide and enters card sats-back as Reward.

From 1.2.6 (new to you if you're updating from 1.2.5:0 or earlier)

Fixes that change tax figures

• Income deposits after an edit. Changing an Income, Interest or Reward deposit's amount or date could keep its old value, and moving one from Bank to the Wallet or Exchange BTC with an AI assistant or the API could leave it at $0. All earlier versions, any tax year. What to do: open Settings > Ledger Review and check each income deposit it lists: clear the value to use that day's price, or type the right one.
• Dollar deposits are not bitcoin income. A deposit of dollars (Bank, Exchange USD) marked Income, Interest or Reward that carried a value was counted as bitcoin income; it no longer is. All earlier versions, any tax year. What to do: report dollar interest from your bank's or exchange's own tax form (such as Form 1099-INT or 1099-MISC).
• My BTC and Gift deposits keep their holding period. They can now carry the date the coins were first acquired (by the giver, for a gift), so coins held more than a year count as long-term; before, the holding period started at the deposit. All earlier versions, every tax year with such a sale. What to do: Ledger Review lists My BTC and Gift deposits without that date; add it where you know it, then download your forms again. A date can also change which coins are sold first, so years already filed can change: ask your tax professional whether to amend.
• Card sats-back is not income. A new deposit source, Rebate, for bitcoin back for spending, such as a rewards card's sats-back: valued like income, its value when received is its cost basis, but it isn't counted as income. Entered as Reward, such bitcoin was counted as income, in every earlier version and tax year. What to do: change card or shopping rewards from Reward to Rebate (the value stays); keep mining, staking and bonuses as Reward; ask your tax professional if unsure.

IRS forms and reports

• Losses print in parentheses, as the IRS asks; tiny amounts print in full (0.00000005 BTC, not 5E-8); no more blank Form 8949 pages.
• The Complete Tax Report has a page for whoever files your return: what BitcoinTX fills on Form 8949 and Schedule D, what it leaves blank and why.
• Ledger Review lists income deposits with a $0 or blank value.

Smaller fixes

• For a Gift deposit, the transaction form now asks for the giver's cost basis.
• Connect an AI Assistant's Claude Code command sets up the connector for every folder, not only the one you ran it in. If you set it up with the old command, the changelog linked below says how to move it.

One wallet, one exchange

• BitcoinTX now states plainly that it's built for one self-custody wallet and one exchange account, and why: since 2025, IRS rules figure cost basis wallet by wallet.
• It also says it's software, not tax advice: check its figures with a tax professional before you file.

Coming from 1.2.4:0 or earlier? Set Login Credentials replaces Show Credentials and Reset Login Credentials; your login stays. Only if StartOS keeps no password for you, run Set Login Credentials when StartOS asks for it; it replaces any username and password you set inside BitcoinTX.

Everything in 1.2.7 and 1.2.6

SHA256 Hashes

05a7a4a4bbf898899c3df4c6626ee46138bae909283aeb4a5286a1219102776d  btctx_aarch64.s9pk
fdaffa83a4a2e52438c028a15bfc84f3018e6ea6249061036404fd72174a37cc  btctx_x86_64.s9pk

1.2.6:0

What's Changed

BitcoinTX 1.2.6 fixes what testing the 2026 forms turned up, and says plainly who BitcoinTX is for.

Fixes that change tax figures

• Income deposits after an edit. Changing an Income, Interest or Reward deposit's amount or date could keep its old value, and moving one from Bank to the Wallet or Exchange BTC with an AI assistant or the API could leave it at $0. All earlier versions, any tax year. What to do: open Settings > Ledger Review and check each income deposit it lists: clear the value to use that day's price, or type the right one.
• Dollar deposits are not bitcoin income. A deposit of dollars (Bank, Exchange USD) marked Income, Interest or Reward that carried a value was counted as bitcoin income; it no longer is. All earlier versions, any tax year. What to do: report dollar interest from your bank's or exchange's own tax form (such as Form 1099-INT or 1099-MISC).
• My BTC and Gift deposits keep their holding period. They can now carry the date the coins were first acquired (by the giver, for a gift), so coins held more than a year count as long-term; before, the holding period started at the deposit. All earlier versions, every tax year with such a sale. What to do: Ledger Review lists My BTC and Gift deposits without that date; add it where you know it, then download your forms again. A date can also change which coins are sold first, so years already filed can change: ask your tax professional whether to amend.
• Card sats-back is not income. A new deposit source, Rebate, for bitcoin back for spending, such as a rewards card's sats-back: valued like income, its value when received is its cost basis, but it isn't counted as income. Entered as Reward, such bitcoin was counted as income, in every earlier version and tax year. What to do: change card or shopping rewards from Reward to Rebate (the value stays); keep mining, staking and bonuses as Reward; ask your tax professional if unsure.

IRS forms and reports

• Losses print in parentheses, as the IRS asks; tiny amounts print in full (0.00000005 BTC, not 5E-8); no more blank Form 8949 pages.
• The Complete Tax Report has a page for whoever files your return: what BitcoinTX fills on Form 8949 and Schedule D, what it leaves blank and why.
• Ledger Review lists income deposits with a $0 or blank value.

Smaller fixes

• For a Gift deposit, the transaction form now asks for the giver's cost basis.
• Connect an AI Assistant's Claude Code command sets up the connector for every folder, not only the one you ran it in. If you set it up with the old command, the changelog linked below says how to move it.

One wallet, one exchange

• BitcoinTX now states plainly that it's built for one self-custody wallet and one exchange account, and why: since 2025, IRS rules figure cost basis wallet by wallet.
• It also says it's software, not tax advice: check its figures with a tax professional before you file.

Update your AI connector too

• Using an AI assistant with BitcoinTX? In your AI app's configuration, change the version after btctx-mcp== to 1.2.6 (Connect an AI Assistant shows it) and restart the AI app. Your AI key stays the same. Otherwise the assistant keeps its old guide and enters card sats-back as Reward.

Coming from 1.2.4:0 or earlier? Set Login Credentials replaces Show Credentials and Reset Login Credentials; your login stays. Only if StartOS keeps no password for you, run Set Login Credentials when StartOS asks for it; it replaces any username and password you set inside BitcoinTX.

Everything in 1.2.6

SHA256 Hashes

6e2fe17fcfb410843f5cf4c19e30557e4e1784bc314c8865cc254feb1386e8f0  btctx_aarch64.s9pk
18a04cc7db396352dc5e22d6238cf0c18e7ab1dc6638a91b22b17b4fd534f1d8  btctx_x86_64.s9pk

1.2.5:0

What's Changed

BitcoinTX 1.2.5 brings a preview of the 2026 tax forms. Until the IRS publishes the final ones, Reports offers 2026 filled in on the IRS's draft Form 8949 and Schedule D, marked "DRAFT — DO NOT FILE" on every page: use them to check your figures, never to file. The preview ends by itself at the end of 2026; the final forms come in an update. On a phone, the panel for adding or editing a transaction now has a close button (✕). The Complete Tax Report is redesigned, with the same figures: a cover with the year's key figures, a one-page summary showing each Form 8949 box with its Schedule D line, and clearer tables with totals; its almost always empty "Expenses" section is gone. Reports also offers the Transaction History as a PDF (choose the format), now fitting the page. Every component BitcoinTX is built from is now locked to an exact, verified version. Connect an AI Assistant shows the root CA certificate and the Claude Desktop configuration with their line breaks, and offers the certificate as a download. Price Source & Privacy explains what each price source does. Coming from 1.2.4:0 or earlier? Set Login Credentials replaces Show Credentials and Reset Login Credentials: it makes a new password and shows it once. Your login stays; only if StartOS keeps no password for you, stop BitcoinTX and run Set Login Credentials before starting it again; it replaces any username and password you set inside BitcoinTX. Coming from 1.2.1 or earlier? After updating, open Settings > Ledger Review in BitcoinTX, and if it lists figures a recalculation would change, run Recalculate Ledger. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

6bd4ff3c6a20a69a41432e8bf51e9ade2786712c053941296d4ad19c9d6e1e3b  btctx_aarch64.s9pk
434a49679388c409992c8ee2c384cf92664154e51fdf532741d82470c5a3af01  btctx_x86_64.s9pk

1.2.4:0

What's Changed

BitcoinTX 1.2.4 brings small fixes found by testing 1.2.3, with no change to any tax figure. A CSV export imported again now keeps a fee of 0 as 0 instead of dropping it. On a phone, every tab in the top bar fits on screen, Logout included. Escape closes the panel for adding or editing a transaction, asking first if you have unsaved changes. An unused transaction lock that nothing could switch on was removed; this updates the database once (a copy of it is kept first). Coming from 1.2.1 or earlier? You also get 1.2.2's tax-figure fixes and 1.2.3's code cleanup: after updating, open Settings > Ledger Review in BitcoinTX, and if it lists figures a recalculation would change, run Recalculate Ledger. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

37fecd0141bed0aecb615692b5391854ca1a512753cf04ac3cd5cb1c26b1eb14  btctx_aarch64.s9pk
4b78e339d3cea7fd829cd4091de6a956859283d3709cd5a7959fab202d7a9ae8  btctx_x86_64.s9pk

1.2.3:0

What's Changed

BitcoinTX 1.2.3 is a maintenance release with no new features: the code behind the app was reorganized to be easier to maintain, and every tax figure, form, report and CSV was checked to come out exactly as in 1.2.2. Two small fixes: a CSV import file with an unexpected value in its fee_usd_typed column now shows an error on that row instead of failing, and Ledger Review now reports a problem it meets while checking fee values instead of quietly skipping the transfer. Coming from 1.2.1 or earlier? You also get BitcoinTX 1.2.2, a stability release with no new features. It fixes tax figures in cases found by a bug hunt: a sale could drop off Form 8949 after the AI assistant changed a transaction's type, a fee entered without its currency wasn't counted, pay the AI added as income into a dollar account was valued at the bitcoin price, and a re-imported CSV could reorder entries made at the same time. Form 8949's Totals line is now filled in. Privacy: the AI connector no longer writes your transaction dates to its log, restoring a backup keeps your price settings, deleted entries are erased from the database, and every public price site is named and asked less often. After updating, open Settings > Ledger Review in BitcoinTX: if it lists figures a recalculation would change, run Recalculate Ledger. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

c616e29eeb7e6a6c1e2df87096eafea87600ff0ac6cbd53ed4034bc9348adc1c  btctx_aarch64.s9pk
6dcabed9bf111f767446cf529bfd1889c45f567e11e1ff25533f97fe8dadcd6e  btctx_x86_64.s9pk

1.2.2:1

What's Changed

The StartOS icon is now BitcoinTX's own logo, the same one the app shows; nothing else changes in this package update. Coming from 1.2.1 or earlier? You also get BitcoinTX 1.2.2, a stability release with no new features. It fixes tax figures in cases found by a bug hunt: a sale could drop off Form 8949 after the AI assistant changed a transaction's type, a fee entered without its currency wasn't counted, pay the AI added as income into a dollar account was valued at the bitcoin price, and a re-imported CSV could reorder entries made at the same time. Form 8949's Totals line is now filled in. Privacy: the AI connector no longer writes your transaction dates to its log, restoring a backup keeps your price settings, deleted entries are erased from the database, and every public price site is named and asked less often. After updating, open Settings > Ledger Review in BitcoinTX: if it lists figures a recalculation would change, run Recalculate Ledger. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

7038cdafb2b17ac47072770513c36c0cb98c5765a459ca80920c9ff826cb79a6  btctx_aarch64.s9pk
92596887f653ecc8984d5e2212a5a5cde21e6e66e47a918a636922d4d7b20dd0  btctx_x86_64.s9pk

1.2.2:0

What's Changed

BitcoinTX 1.2.2 is a stability release with no new features. It fixes tax figures in cases found by a bug hunt: a sale could drop off Form 8949 after the AI assistant changed a transaction's type, a fee entered without its currency wasn't counted, pay the AI added as income into a dollar account was valued at the bitcoin price, and a re-imported CSV could reorder entries made at the same time. Form 8949's Totals line is now filled in. Privacy: the AI connector no longer writes your transaction dates to its log, restoring a backup keeps your price settings, deleted entries are erased from the database, and every public price site is named and asked less often. After updating, open Settings > Ledger Review in BitcoinTX: if it lists figures a recalculation would change, run Recalculate Ledger. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

ae6bef30aa1d6674c00f2341f12facf1b83e1a1d991bc4616a6a3365a46a1b53  btctx_aarch64.s9pk
99eeabb7a4bc95b56d95396d75a0e9ca376d5bbc857480fd0ec5a26e13fe4f2f  btctx_x86_64.s9pk

1.2.1:0

What's Changed

BitcoinTX 1.2.1 fixes what testing 1.2.0 found. BitcoinTX no longer turns public price sites on by itself when transactions were added before a price source was chosen; if Price Source & Privacy is set to Choose in BitcoinTX, check Settings > Privacy & Network. Restoring a backup file inside the app now keeps your current login, so Show Credentials stays right. Reports say why they can't be made and which transaction to fix, the Complete Tax Report's holdings on January 1 are right again, and exported CSV files import back unchanged. The log no longer fills up with health checks. Plus smaller fixes and updated components. Everything: https://github.com/DigiMonk73/BTCTX-MCP/blob/main/docs/CHANGELOG.md

SHA256 Hashes

38c812555938e02c205f52099130cec458171f0462baa5adad24ee68a123b268  btctx_aarch64.s9pk
4114f28e3ccdb606d764dabbd52a7f91f638666e96b2263be18ad1bdab41cd38  btctx_x86_64.s9pk