discussion about mocacinno and HCP free submission service

[mocacinno]

After getting trolled, i moved the topic to a self-moderated thread: https://bitcointalk.org/index.php?topic=1943939
This unmoderated thread can now be used for discussion about this service!

[1714121179]

1714121179

[HCP]

As discussed with mocacinno via PM, I'm just posting here to state that I will be assisting him with this...

Hopefully, I can fill the gaps when he isn't online

TIP address: 1PMu6KrSGBmJ5EQ7siUXcshFAE55bFDrxk

[johnsmithx]

Reply on this topic, post following info:

• the transaction id
• wether or not you're the sender or the receiver (or both)
• which addresses belong to your wallet (also list the change addresses). I can also work the other way around: in this case, tell me which address you were trying to fund
• which wallet software you're using
• acknowledge that your transaction is in my mempool (check requirement 2 ^^)
• acknowledge there's nothing "strange" going on with your transaction
• acknowledge you will rectify your situation, so that in the future you'll add sufficient fees... I will not help accelerate transactions for freeloaders that just keep cheaping out on the fees!!!
• if you tipped me, you can list the transaction id of the tip (not required)

What a great way to make stupid people publicly reveal their btc addresses, ownership, wallet software and other details. Excellent idea indeed. Big brother is surely very proud of you.

[mocacinno]

Reply on this topic, post following info:

• the transaction id
• wether or not you're the sender or the receiver (or both)
• which addresses belong to your wallet (also list the change addresses). I can also work the other way around: in this case, tell me which address you were trying to fund
• which wallet software you're using
• acknowledge that your transaction is in my mempool (check requirement 2 ^^)
• acknowledge there's nothing "strange" going on with your transaction
• acknowledge you will rectify your situation, so that in the future you'll add sufficient fees... I will not help accelerate transactions for freeloaders that just keep cheaping out on the fees!!!
• if you tipped me, you can list the transaction id of the tip (not required)

What a great way to make stupid people publicly reveal their btc addresses, ownership, wallet software and other details. Excellent idea indeed. Big brother is surely very proud of you.

Are you calling me a scammer or just an idiot? There are dozens of people asking for help with their stuck transactions every single day. I've been trying to help them, and i know from experience that without this information it is hard to help them. If they don't want to give out this info, it's their own choice, i'm defenatly not forcing anybody to use my [free] service... It's not like i'm asking their private key anyways (and i never will), all info i ask is either already visible publicly, or not important (AFAIK)... The only thing that happens is that their addres can be tied to their bitcointalk username AND that i'll try to solve their problem.

The reason for asking this info:
transaction id => the transaction should already be in the mempool of a lot of nodes (see requirements), so it is already public knowledge... There isn't much i can do to help them without the txid anyways...
sender or receiver => i think it's rather hard to help someone without knowing if they can do a CPFP, or double spend the inputs...
which addresses are theirs => i don't want to spend time creating a CPFP using outputs to an address for which the user doesn't own the key
which wallet software => impossible to guide them trough signing a CPFP if i don't know which wallet they're using
acknowledgement of the transaction being in my mempool => don't want to spend time looking up transactions that have a high probability of having dust outputs, unconfirmed parents,... If it's in my node, it has a high chance of being "clean"
acknowledgement of nothing strange going on => same as point above
acknowledgement of user having fixed the problem => making sure i don't have to help the same person twice

For everybody wanting to use this service: if you give me the information i request, there is a chance law enforcement can potentially link your forum identity to the wallet used to send/receive. IF you're either a privacy concerned user, or you're doing something illegal, it might be unwise to ask for my help by posting the information requested in the OP

[m8rgr8]

so i have created the signed alternative transaction (FRBF) , to my previous one.
however it still says txn-mempool-conflict, or at your node (unsuccesfull ... )

https://blockchain.info/de/tx/c277e2d5565891253a709fc889588dd52dc53daa8e70149a4ba5874c5cd3bc0f

the new signed transaction is:
0100000001023258b7b3d634b7faddacedb74496797f61d72de1ede1ecb074c42976a71c1a00000 0006a47304402207ca8badbd88475663b0031a12ce6ad7aec6aed76b663e43484593080146d89af 0220664dce3b3bbb8ea44479ce1f7d63963ca0e17df3d79bd8867eabd19006f21e310121031ff84 da6ed94365fb717a65e2a21c61659a16303ee05f495a906a723fc321c9affffffff026e05090000 0000001976a91438c8e0e141361d45cb2075f30c8a4886ac59dc2c88ac20c5fb00000000001976a 914d617825f13002fe8852f77a2df6742440733d63d88ac00000000

it simply wont go into the mempool ...

[mocacinno]

so i have created the signed alternative transaction (FRBF) , to my previous one.
however it still says txn-mempool-conflict, or at your node (unsuccesfull ... )

https://blockchain.info/de/tx/c277e2d5565891253a709fc889588dd52dc53daa8e70149a4ba5874c5cd3bc0f

the new signed transaction is:
0100000001023258b7b3d634b7faddacedb74496797f61d72de1ede1ecb074c42976a71c1a00000 0006a47304402207ca8badbd88475663b0031a12ce6ad7aec6aed76b663e43484593080146d89af 0220664dce3b3bbb8ea44479ce1f7d63963ca0e17df3d79bd8867eabd19006f21e310121031ff84 da6ed94365fb717a65e2a21c61659a16303ee05f495a906a723fc321c9affffffff026e05090000 0000001976a91438c8e0e141361d45cb2075f30c8a4886ac59dc2c88ac20c5fb00000000001976a 914d617825f13002fe8852f77a2df6742440733d63d88ac00000000

it simply wont go into the mempool ...

Since most info was missing, the only thing i could do was submitting it to viabtc... Your origibal tx should go in the following block they mine

[m8rgr8]

so i have created the signed alternative transaction (FRBF) , to my previous one.
however it still says txn-mempool-conflict, or at your node (unsuccesfull ... )

https://blockchain.info/de/tx/c277e2d5565891253a709fc889588dd52dc53daa8e70149a4ba5874c5cd3bc0f

the new signed transaction is:
0100000001023258b7b3d634b7faddacedb74496797f61d72de1ede1ecb074c42976a71c1a00000 0006a47304402207ca8badbd88475663b0031a12ce6ad7aec6aed76b663e43484593080146d89af 0220664dce3b3bbb8ea44479ce1f7d63963ca0e17df3d79bd8867eabd19006f21e310121031ff84 da6ed94365fb717a65e2a21c61659a16303ee05f495a906a723fc321c9affffffff026e05090000 0000001976a91438c8e0e141361d45cb2075f30c8a4886ac59dc2c88ac20c5fb00000000001976a 914d617825f13002fe8852f77a2df6742440733d63d88ac00000000

it simply wont go into the mempool ...

Since most info was missing, the only thing i could do was submitting it to viabtc... Your origibal tx should go in the following block they mine

that sounds good. thanks.
what further info do you need ?

[mocacinno]

so i have created the signed alternative transaction (FRBF) , to my previous one.
however it still says txn-mempool-conflict, or at your node (unsuccesfull ... )

https://blockchain.info/de/tx/c277e2d5565891253a709fc889588dd52dc53daa8e70149a4ba5874c5cd3bc0f

the new signed transaction is:
0100000001023258b7b3d634b7faddacedb74496797f61d72de1ede1ecb074c42976a71c1a00000 0006a47304402207ca8badbd88475663b0031a12ce6ad7aec6aed76b663e43484593080146d89af 0220664dce3b3bbb8ea44479ce1f7d63963ca0e17df3d79bd8867eabd19006f21e310121031ff84 da6ed94365fb717a65e2a21c61659a16303ee05f495a906a723fc321c9affffffff026e05090000 0000001976a91438c8e0e141361d45cb2075f30c8a4886ac59dc2c88ac20c5fb00000000001976a 914d617825f13002fe8852f77a2df6742440733d63d88ac00000000

it simply wont go into the mempool ...

Since most info was missing, the only thing i could do was submitting it to viabtc... Your origibal tx should go in the following block they mine

that sounds good. thanks.
what further info do you need ?

Nothing, it's done
Your tx should be in a block in 3-4 hours (on average)

What a great way to make stupid people . . .
- snip -

If you don't want to deal with unrelated nonsense in the thread, I'd suggest locking this thread and starting an identical new one with "self-moderated" marked.  That way you can purge the thread of un-necessary, unhelpful posts.

Note:  I realize this post is just adding to the noise.  I'll delete this post once I think you've seen it.

Thanks for the tip HCP had the same idear... I'll probably take the advice if any more of those posts start coming up...
No need to delete your post, i don't mind it.

[mocacinno]

What a great way to make stupid people publicly reveal their btc addresses, ownership, wallet software and other details. Excellent idea indeed. Big brother is surely very proud of you.

~snip~
Are you calling me a scammer or just an idiot?
~snip~

Never mind... After reading what you wrote on my trustpage, i now see you're calling me a scammer... Apparently, somebody risked 999,999BTC by using my FREE service that only requested information that is either publicly available, or completely harmless to give out.

You did have one point: all information given in a public thread is publicly available, and can be read by anyone, including law enforcement... Anybody not smart enough to understand this basic fact about a public forum shouldn't be here in the first place.



I'm just asking myself: is it possible you tried to be a keyboard warrior, called me out by claiming something so obvious (and harmless) that most people wouldn't even think about it, read my reply, didn't know what to answer, felt butthurt and decided to post a nice red tag claiming that i'm scamming over 2 million USD (at current preev rate) on my trustwall? Just a theory here

[DannyHamilton]

mocacinno,

I'm not sure how familiar you are with using encryption tools such as GPG, but you might be able to reduce some concerns others have about revealing wallet and address information publicly if you include a public key in your top post and offer to accept encrypted messages in your service thread.

Obviously YOU would still have access to all the requested information, which may be a concern for some, but at least the information wouldn't turn up on internet search engine results or be available for others to read without your permission.


On the other hand, my guess is that most of the types of people that will need your help aren't going to know how to use your public key to encrypt their post anyhow.

[mocacinno]

mocacinno,

I'm not sure how familiar you are with using encryption tools such as GPG, but you might be able to reduce some concerns others have about revealing wallet and address information publicly if you include a public key in your top post and offer to accept encrypted messages in your service thread.

Obviously YOU would still have access to all the requested information, which may be a concern for some, but at least the information wouldn't turn up on internet search engine results or be available for others to read without your permission.


On the other hand, my guess is that most of the types of people that will need your help aren't going to know how to use your public key to encrypt their post anyhow.

Actually that's a great idear
As a matter of fact, they can use keybase.io as an easy way to encrypt their messages. But you're right, i'd still be able to decrypt them, and it would be an extra step i'd have to take... I'm defenately not against it tough.
Also, HCP said he'd help me out, so it would be best if the users encrypted their data twice (with both our public keys), and posted the identical data encrypted with each seperate public key. (don't know if HCP is willing to do this, but i'll ask him).

I'll update my OP when i'm back at the office!

[DannyHamilton]

Also, HCP said he'd help me out, so it would be best if the users encrypted their data twice (with both our public keys), and posted the identical data encrypted with each seperate public key. (don't know if HCP is willing to do this, but i'll ask him).

Or....


Instead of using your personal public key, you could generate a new public key exclusively for this service.  Then you and HCP could both have  copy of that private key.  That way the users would only need to encrypt once, and either of you could decrypt.

Again, it does mean that those requesting assistance will need to provide private information to BOTH of you and to trust that you won't share it, but that's the nature of getting help.  If they don't want to do that, they don't have to ask you for help.

At least the info won't come up in search results and such.