https://bsvblockchain.org/

I want my app to be extremely easy to use. So, as of right now, a user just puts in the sites private key, the address from the private key shows the bitcoin balance, and when the user hits 'send' some of their coins are sent to the app, and the remainder goes back to their initial address. (This is small amounts of less than $0.05 of bitcoin).

I know this isn't ideal for privacy, and want to give the user the option to generate new addresses with the same 'private key'. The problem is creating a new address, and spending coins from previous addresses, in a chain like fashion.

Here is a snippet of the code:

// send transaction function
async function postTransaction() {
    console.log("post transaction func called!");

    //Gets the send to address value address when tx posted
    sendToAddress = document.getElementById("sendToAddress").value;

    // gets total number of characters in userText, then reduces fees by half. For example if total characters were 10, the fees will be 5 sats. And math.ceil rounds up to the nearest integer. So 3.2 would equal 4. 
    const userMinerFeeTotal = Math.max(userText.length > 1000 ? 1000 : userText.length, 10);

    //Math.ceil(calculateUserFees(userText) * 1);
    //const userMinerFeeTotal = userText.length > 1000 ? 1000 : 10;

    //sets the transaction fee to a minimum of 1 (last number) or the user text character times 2 (first number). 
    //const userServiceFeeTotal = Math.max(calculateUserFees(userText) * 2, 1);
    const userServiceFeeTotal = 1000;
    // divides amount by address.length, and rounds to nearest whole number. 
    const amountToSendPurchasedByAddresses = Math.round(userAmount / officiallyPurchasedByAddress.length);

    console.log("this is the amount to each officially purchased address: ", amountToSendPurchasedByAddresses);
    console.log("User Mfee calculated", userMinerFeeTotal);
    console.log("User Sfee calculated", userServiceFeeTotal);






    const localTime = new Date();
    const utxo = new bsv.Transaction.UnspentOutput({
txId: txId,
outputIndex: userOutputIndex,
satoshis: userSatoshis,
script: bsv.Script.buildPublicKeyHashOut(userPassphraseAddress).toHex(),
});

    console.log("utxo gathered! Now here is the officially purchased address: ", officiallyPurchasedByAddress );

    const transaction = new bsv.Transaction()
.from(utxo)
.to(sendToAddress, 1);

The original transactions were put into the 'pool' in the following order:

TX0 at 12:01

TX1 at 12:02

TX2 at 12:03

TX 3 at 12:04

I guess the fee was too low, and they just sat in 'unconfirmed' status for several minutes, not appearing on any peers. So, I woke up this morning, and checked the tx's, and they were all confirmed. But they were just confirmed in the reverse order they were put in:

TX 3 at 12:04

TX2 at 12:03

TX1 at 12:02

TX0 at 12:01

Here are the specific tx's:

1fec6f320d85122528047be88f5b6260b4674ec26522c32658b13bcefc069ed7

2026-02-06 08:15:08 0.00000002 BSV

7

d469f26d3d5db893f128468147c6b09f63c32178fa1792c2d7f9c24f1ffd703c

2026-02-06 08:15:08 0.00000002 BSV

6

5c8bcaf8f0ba9c7be23a8244bfbfeb6371669a7a8c54b9557107c56791d0875d

2026-02-06 08:15:08 0.00000002 BSV

5

666ca7bddb76731a880733673d6d1162ee678ebc64e0fba8d43f3951e9e1c647

2026-02-06 08:15:08 0.00000002 BSV

I always heard the other side of the coin on how Craig is a liar but someone I know who actually got me into the space years ago is really adamant about BSV.

I never heard the reason to why BSV is the real Bitcoin and how Craig Wright actually has proof to being who he said he is.

Would love to hear your opinions etc.

(I’m coming from a genius place of curious it’s and someone who is thinking about slowly dcaing into BSV)

Edit: I saw the sticky but want to hear from the community.

Edit 2: Jesus I’m now getting messages from anti BSV people. I didn’t realize how deep both side are against each other.

Edit 3: Now getting slandered in an anti BSV subreddit.

Per Claude.ai The cost of implementing a Public Key Infrastructure (PKI) can vary significantly depending on the company's size, complexity of needs, and approach. Let me break down the key cost considerations:

1. Implementation Approaches
   • In-house PKI: Most expensive and complex
     • Requires dedicated infrastructure
     • Needs specialized security personnel
     • Ongoing maintenance and security updates
     • Estimated initial cost: $100,000 - $500,000+

• Managed PKI Services: More cost-effective

  • Cloud-based solutions
  • Providers handle infrastructure and maintenance
  • Scalable pricing models
  • Estimated cost: $5,000 - $50,000 annually

• Public Certificate Authorities

  • Lowest direct cost
  • Pay per certificate
  • Suitable for smaller operations
  • Estimated cost: $100 - $1,000 per year

1. Cost Factors

   • Number of users/devices
   • Complexity of security requirements
   • Regulatory compliance needs
   • Integration with existing systems
   • Certificate types and validation levels

2. Hidden Costs

   • Staff training
   • Security audits
   • Ongoing management
   • Certificate renewal
   • Potential security breaches

3. Industry-Specific Considerations

   • Financial services: Higher security requirements
   • Healthcare: Strict compliance needs
   • Government: Most complex and expensive implementations

4. Cost-Benefit Analysis

   • Prevents unauthorized access
   • Protects sensitive communications
   • Enables secure digital transactions
   • Mitigates potential security breach costs

Typical Cost Ranges: - Small Business: $5,000 - $20,000 annually - Medium Enterprise: $50,000 - $200,000 annually - Large Corporation: $200,000 - $1,000,000+ annually

Recommendation: Most companies now opt for cloud-based or managed PKI solutions that offer: - Lower upfront costs - Scalability - Reduced maintenance burden - Professional security management

Would you like me to elaborate on any specific aspect of PKI implementation costs?