The possibility that @Richman2025 happened is that BlueWallet generated a new incoming address after the first transaction. This is normal behavior as your Bitcoin wallet uses different addresses for privacy, but they all still belong to your wallet as long as you use the correct one. If the withdrawal is sent to an address that belongs to your Blue Wallet, you should see the funds when the transaction is on-chain. If sent elsewhere, recovery may not be possible without a private key. The first step is to check the transaction ID in Blockchain Explorer to see exactly where the funds went.

As everyone knows, one bitcoin is 1000000 Satoshi.

So, for example, 1234567890123 Satoshi is 1234.567890123 Bitcoin.

When pointing to a regular web browser with https://blockchain.info/q/addressbalance/1a1zp1ep5qgefi2dmptftl5slmv7divfna

10297591076

When doing the same with https://blockchair.com/bitcoin/address/1a1zp1ep5qgefi2dmptftl5slmv7divfna, that reply

Main Balance + 102.97591076 BTC

Therefore, the reaction you are seeing is in Sato’s integer unit.

Just do floating point splitting of blockchain answers at 10⁸ To get the decimal answer if that’s what you’re looking for.

Moxie founder Neonwight outlined the platform’s strategy for combining artificial intelligence (AI) with crypto to create “Sex Capital Markets.”

He said the controversial concept was fundamentally about financial inclusivity and unlocking productivity for marginalized creators. 

He stated in an interview with CryptoSlate:

“Adult creators are one of the most marginalized professions in society. Banks refuse to serve them, and Visa and Mastercard charge north of 10% to 15% processing fees because they view adult content as legal and reputational risk.”

Neonwight detailed personal experiences with banking discrimination, citing instances where his bank blocked OnlyFans payments after two transactions. The bank told him it does not “serve payments in those kinds of industries.”

Neonwight provided specific data on creator earnings, noting that he reached out to adult content creators who generate between $50,000 and $100,000 monthly revenue, translating to $600,000 to $1.2 million annual recurring revenue. 

Despite these successful business metrics, creators cannot access traditional banking services, business loans, or investment opportunities available to other entrepreneurs. Having a revenue stream fully powered via crypto rails could address the debanking issues faced by adult content creators.

Shifting metas

Moxie was born as an AI agent deployed through the Virtuals Protocol. Users could access Moxie’s services through the Agent Commerce Protocol and commission AI-generated adult content, paying $10 worth of VIRTUAL tokens.

Since then, Moxie has experienced some changes. First, it left the Virtuals platform due to policy issues. Then, the same model of commissioned content was applied to a proprietary platform, but using a pre-set model called Jenny.

As of Aug. 12, Moxie offers a chat that emulates a real conversation, where Jenny sends AI-generated content, and users can pay 400 MOXIE tokens to see it.

According to Neonwight, Moxie targets OnlyFans’ core revenue driver. Over 80% of the platform’s $7 billion annual revenue derives from customized one-on-one content. 

He explained:

“It becomes an issue for very famous content creators because they don’t have time to split among their huge fan base. There’s also an issue where, as they get older, it gets more taxing to do particular scenes.”

Moxie’s AI solution enables creators to serve larger audiences while maintaining personal connections through personality-trained chatbots. 

The platform uses a custom-trained video model developed by an AI researcher formerly at Alibaba. The proprietary large language model creates content that allows creators to fulfill requests they might not personally perform while preserving their authentic personality traits.

Strategic partnerships

The platform’s partnership structure maintains human contact while expanding creative possibilities. 

Moxie partnered with model Tori Sweetie to curate AI-generated content and participate through live streaming. The goal is to ensure authentic personality representation while enabling content categories that they might not personally create.

Neonwight said:

“The one-to-one human connection is what sells right now. The AI chatbot is trained based on her personality, and she will stream on our platform to give fans another level of personality interaction.”

Martina Oliveira is a top creator on Privacy, Brazil’s leading adult content platform. She provided a perspective on AI’s impact on the adult content industry. 

When asked about AI-generated adult content potentially harming content creators’ revenue, Oliveira said: 

“I think it hurts real models because some content creators who didn’t record videos, claiming they recorded them just by being pretty, are already doing this. I believe that to get attention now, you have to have more originality, you have to talk, you have to expose yourself more because there are already AIs doing the basics, you have to do more than that.”

However, she noted AI-generated content currently has limitations in video quality, particularly for explicit content.

Furthermore, there is the possibility to partner with platforms that generate AI content, such as Moxie, to increase productivity and test new content.

Oliveira previously worked with a platform offering voice synthesis services where users paid per minute for AI-generated conversations. 

According to her:

“I would definitely close this type of partnership, especially if it generated images, I think that’s what was missing in what I did before.”

Regarding crypto integration with platforms like Privacy and OnlyFans, Oliveira acknowledged potential benefits but noted platform resistance to change. 

She believes crypto will be used on these sites over the years because it makes transactions safer. However, Oliveira concluded:

“But it might take a long time because platforms are kind of reluctant to spend on adding services to the site because they don’t know if it will work.”

I’m trying to create a transfer script.

The entire script was provided below

import * as bitcoin from "bitcoinjs-lib";
import * as tinysecp from "tiny-secp256k1";
import axios from "axios";
import ECPairFactory from "ecpair";

const ECPair = ECPairFactory(tinysecp);
bitcoin.initEccLib(tinysecp);

const NETWORK = bitcoin.networks.testnet;
const MEMPOOL_API = "https://mempool.space/testnet/api";

// Helper function to validate UTXO
function validateUtxo(utxo: any): void {
  if (
    !utxo.txid ||
    typeof utxo.vout !== "number" ||
    typeof utxo.value !== "number"
  ) {
    throw new Error("Invalid UTXO structure");
  }
  if (!/^(a-fA-F0-9){64}$/.test(utxo.txid)) {
    throw new Error("Invalid UTXO txid format");
  }
}

export async function sendBTC_P2TR({
  wif,
  recipient,
  amountSats,
}: {
  wif: string;
  recipient: string;
  amountSats: number;
}): Promise<{ success: boolean; message: string; txId?: string }> {
  try {
    console.log("🏁 Starting transaction process...");

    // Input validation
    if (!wif || !recipient || !amountSats) {
      throw new Error("Missing required parameters");
    }
    if (typeof amountSats !== "number" || amountSats <= 0) {
      throw new Error("Invalid amount");
    }
    if (!recipient.startsWith("tb1p")) {
      throw new Error("Recipient must be a Taproot testnet address");
    }

    // Key derivation
    const keyPair = ECPair.fromWIF(wif, NETWORK);
    if (!keyPair.privateKey) throw new Error("No private key derived from WIF");

    const privateKey = keyPair.privateKey;
    const internalPubkey = Buffer.from(
      tinysecp.pointFromScalar(privateKey, true)!.slice(1)
    );

    const p2tr = bitcoin.payments.p2tr({ internalPubkey, network: NETWORK });
    const address = p2tr.address!;
    const scriptPubKey = p2tr.output!;

    console.log("📬 Sender Taproot address:", address);

    // Fetch UTXOs
    const { data: utxos } = await axios.get(
      `${MEMPOOL_API}/address/${address}/utxo`
    );
    if (!utxos.length) return { success: false, message: "No UTXOs found" };

    // Estimate fee
    const { data: fees } = await axios.get(
      `${MEMPOOL_API}/v1/fees/recommended`
    );
    const feeRate = Math.max(fees.hourFee || 1, 2);
    const fee = Math.ceil(feeRate * 110); // Estimated vsize for P2TR

    // Select UTXO
    const utxo = utxos.find((u: any) => u.value >= amountSats + fee);
    if (!utxo)
      return {
        success: false,
        message: `No suitable UTXO found (needed ${amountSats + fee} sats)`,
      };

    // Key tweaking
    const tweak = bitcoin.crypto.taggedHash("TapTweak", internalPubkey);
    let tweakedPrivKey = tinysecp.privateAdd(privateKey, tweak);
    if (!tweakedPrivKey) throw new Error("Failed to tweak private key");

    // Build PSBT
    const psbt = new bitcoin.Psbt({ network: NETWORK });
    psbt.addInput({
      hash: utxo.txid,
      index: utxo.vout,
      witnessUtxo: { script: scriptPubKey, value: utxo.value },
      tapInternalKey: internalPubkey,
    });

    psbt.addOutput({ address: recipient, value: amountSats });
    const change = utxo.value - amountSats - fee;
    if (change > 294) {
      // Dust limit
      psbt.addOutput({ address, value: change });
    }

    // Signing (fixed approach)
    const tx = (psbt as any).__CACHE.__TX as bitcoin.Transaction;
    const hash = tx.hashForWitnessV1(0, (scriptPubKey), (utxo.value), 0x00);
    const signature = Buffer.from(tinysecp.signSchnorr(hash, tweakedPrivKey));

    // Update with proper signature format
    psbt.updateInput(0, {
      tapKeySig: signature,
    });

    // Final verification
    const validator = (pubkey: Buffer, msghash: Buffer, sig: Buffer) => {
      return tinysecp.verifySchnorr(msghash, pubkey, sig);
    };
    psbt.validateSignaturesOfInput(0, validator);

    psbt.finalizeAllInputs();
    const txHex = psbt.extractTransaction().toHex();

    // Broadcast
    const { data: txId } = await axios.post(`${MEMPOOL_API}/tx`, txHex, {
      headers: { "Content-Type": "text/plain" },
    });

    return { success: true, message: "Transaction broadcasted", txId };
  } catch (error: any) {
    console.error("Transaction failed:", error.message);
    return {
      success: false,
      message: error?.response?.data || error?.message || "Unknown error",
    };
  }
}

However, I’m facing an error that I can’t understand why

Transaction failed: Request failed with status code 400
❌ Transaction failed: sendrawtransaction RPC error: {"code":-26,"message":"mandatory-script-verify-flag-failed (Invalid Schnorr signature)"}

I bought Bitcoin at the Bitconoma Merica Kiosk ATM in 2022, but I have not done anything more. I was planning to transfer Bitcoin to the cash app BTC Wallet, but as Bitcoin went out of business in 2023, the website and customer service numbers were already there so I hadn’t found a way to access the wallet. The receipt documents I have will display the transaction ID, public wallet address and private key. I entered a public address in a Google search and came up with the amount of BTC and the last date of access in 2022, but it didn’t offer any options to access wallets or options. So I searched for the private key and nothing came up. Can you still access that Bitcoin?

So I fully know how to deposit Bitcoin, but just go up to circle K and click (numbers) to verify the pins and check them out.

I am using the BlockStream app on my Android smartphone. Previously, when it comes to lightning and liquids, we dealt with chain coins.

So when you click on receive in the blockstream app, you have the option from

• Bitcoin
• Bitcoin (lightning)
• Liquid Bitcoin

What is the difference between lightning and liquid here? Both will ask me for the amount I give and generate it invoice After entering the amount. But what do both strings look like?

lightning:LNBC1M1P59Z5MY***

Doesn’t it matter if I got liquid or lightning? As long as this wallet goes, are they both the same?

I previously tried an aqua wallet, and although the liquid address looked different, I also didn’t need a preconceived amount, or just an address.

Also, if I use BTC for retail purchases, how do I convert it to lightning? Blockstream doesn’t seem to provide anything swap option.

I’ve tried several methods to get the Taproot address from the private key using Bitcoinlib, but I’ve continued to get a different address than what you get with a Taproot wallet, such as Unisat or OKX wallet.

Then, after many attempts, I found the command Address.parse And I tried to use it to get all the parameters of the address to replicate it.

Surprisingly, even if you create a class with exactly the same parameters and of course the same private key, the derived addresses will be different.

from bitcoinlib.keys import Key, Address

# keys are for testing purposes
private_key_hex = '25eee8288d42567475d1453843ce57b16b6ba5b6c0661cb2a439fff44c4d455d'
private_key_wif="KxVSwjuqNb6qe3KTLsHG5nYA3WFEqrjyKnGbwgHAreiWsqrwffuh"

k = Key(private_key_wif)
#k.info()
public_key_hex = '02fdf741bc2b1efe52873d748ca438798ad0133b25c388bc50423aed26df8ffbd7'
public_key_hex_uncompressed = '04fdf741bc2b1efe52873d748ca438798ad0133b25c388bc50423aed26df8ffbd7db6b1b700bd2475709f586d7a0105d29b0e4a3017b259e01bc32b220342ab33a'

addr = Address.parse('bc1pfkde37d8chuqa6tgwvp7rwmtl7vvd20ql6g5433xxpdah30t7nushrsrlu')
print(addr.as_dict())

testAddr = Address(
    data = public_key_hex,
    hashed_data = None,
    prefix = 'bc',
    script_type="p2tr",
    compressed = None,
    encoding = 'bech32',
    witness_type="taproot",
    witver = 1,
    depth = None,
    change = None,
    address_index = None,
    network = 'bitcoin',
    network_overrides = None
)
print(testAddr)

I’m not sure if the problem is that it doesn’t have a Bith32M encoding.

If anyone knows how to solve this problem or a workaround, they’ll be really appreciated!

Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure

Eric Trump, son of President Donald Trump, is set to make headlines next month when speaking at the Bitcoin Asia 2025 conference in Hong Kong, amid the presidential family’s growing interest in digital assets.

This event aims to establish the city as a leading hub for digital assets, competing directly with the United States. Under President Trump’s second administration, the United States has made considerable progress in regulating the growth of the crypto market.

A Rising Advocate For Bitcoin And Digital Assets 

In his address, Eric Trump will reportedly explore the long-term potential of Bitcoin, its implications for global finance, and the role Asia plays in shaping the future of Bitcoin adoption, announced by BTC Inc, the organization behind the conference.

Bitcoin Asia is the regional edition of the Bitcoin Conference, one of the largest cryptocurrency events worldwide. The conference made its debut in Hong Kong last May, coinciding with the city’s efforts to cultivate its digital asset sector.

Eric Trump, who co-founded the Bitcoin-mining venture American Bitcoin and is involved in the Trump family-backed initiative World Liberty Financial (WLFI), has been recognized as a prominent advocate for the industry on the international stage. 

Hong Kong Aims For Crypto Dominance

Trump’s participation comes at a pivotal time as Hong Kong intensifies its campaign to become a global leader in digital assets. This ambition aligns with the US government’s goal—during his father’s administration—to establish America as the “crypto capital of the planet.” 

In June, Hong Kong released its “Policy Statement 2.0 on the Development of Digital Assets,” which builds on a blueprint issued in late 2022. This policy outlines the city’s commitment to enhancing its digital asset infrastructure and achieving “new heights of global digital asset leadership.”

The competition for a first-mover advantage in the digital asset space is heating up, particularly as both Hong Kong and the US advance towards the legalization of stablecoins.

US crypto investors are awaiting the approval of bills such as the GENIUS Act and the CLARITY Act by the House. These bills have already secured Senate approval and are awaiting the next move from the House of Representatives before Trump’s signature.

Last year’s Bitcoin Asia conference attracted over 5,500 participants at the Kai Tak Cruise Terminal, with about half of the attendees coming from mainland China. This year, the event is scheduled to take place at the Convention and Exhibition Centre in Wan Chai on August 28 and 29.

When writing, Bitcoin trades at $108,370, down just 3% from its all-time high of $111,800 reached during May’s bullish rally for the crypto market. 

Featured image from NBC, chart from TradingView.com 

Editorial Process for bitcoinist is centered on delivering thoroughly researched, accurate, and unbiased content. We uphold strict sourcing standards, and each page undergoes diligent review by our team of top technology experts and seasoned editors. This process ensures the integrity, relevance, and value of our content for our readers.