/biz/ - Business & Finance

its a scam

>>16754682
> is a scamn

>>16754717
it is

>>16754681
idgaf about this gay shit

parasitic blockchain on bitcoin and claimed via coin burn. this shit needs to go to $0.

i mined $500 about a dollar per fee each and i realised yesterday i could have claimed thousands with that if i used 20 sat fee instead of 100
JUST

>>16754853
i claimed twice using 50 sat fee and didn't succeed

it's not as trivial as it looks

>>16754853
I am an utter brainlet and don't really know how to claim.
Anyone can help?

I am an utter retard and I don't know if I really get how to claim this.
Can somebody help?

I have claimed using 5-15 satoshi/vbyte fees successfully many times over.
Pretty much just sniping for a block being found right after another. And if not the loss is very minimal. I've estimated I can attempt maybe more then 10-20 attempts at 5 sat/vbyte and get at least 5 claims, Rather then put 120 sat/vbyte and have a 90% chance of claim.

Is there any chain analysis you guys are using to better your odds?

>>16755688
Just download the wallet, sync a full node.
Send some satoshi to a p2wsh address.
Then use that address to attempt claims by sending 546 satoshi to the miner address for each claim. Attempt only 1 per block. As only 1 claim can be successful per block. The higher fee you use the higher chances your unseen p2wsh will be the first in the block.

>>16755659
>>16755688
ok
download the wallet from the btc talk thread. generate addresses. make sure to save it etc. then send 0.00000546 BTC to the address (different address each time) with whatever fee depending on how busy network is
your wallet does not need to be synced to claim.

>>16755706
this. sometimes you get 3-4 in a row really fast. its better to use low fee

>>16755743
Yes basically thats how to claim. But you want to also sync a full node. Because without a full node you will not be able to see if your claim was successful, unless you go into an explorer and look through each transaction and try to find the first unseen p2wsh and see if that was yours. (could be possible to create a script for this)

Would highly recommend running a full node to easily see if your claim was successful.

https://jochen-hoenicke.de/queue/#0,2h
Is what I'm using to watch mempool and network activity.

https://blockstream.info/
Is good to check transactions in previous blocks and see stuff.

The times that there is 3-4 in a row really fast is the cheapest way to get in.

>>16755721
Where do I download the wallet and how do I sync a nose? Hell, I don't even know the name of this shitcoin

>>16755825
>how do I sync a nose?

>>16755824
>Yes basically thats how to claim. But you want to also sync a full node
>segwit token

Oh ok I see what's happening here

>>16755825
First read through this thread.
Specifically Natasha Otomoski posts.

https://bitcointalk.org/index.php?topic=5195815.20

Read all Natasha posts before doing anything so you have the full picture of how to properly sync full node.

>>16755866
Theres no denying that Segwit is absolutely needed to be able to create peer to witness script hash.
There is different types of transaction formats on bitcoin. Segwit has enabled several of them.
P2WSH is something that a soft fork of segwit has allowed.

Segwit is backwards compatible. Meaning if your running a node from 2013. You will still be on the same chain is bitcoin.

If you run a btcash node, You will be forked off the original chain. 2013 Node will NOT BE ABLE TO SEE YOUR BCASH. Or BTCSV.

>>16755896

Hi O1G

>>16755906
Not sure what O1G is

Anybody tried the new release? Are stealth addresess worth updating?

>>16755824
this or you can use https://blockchair.com/bitcoin/mempool/transactions?q=has_witness(true)&s=#

tick only
>hash
>fee (usd)
>fee per kwu (btc)
>witness (true)
sort by fee per kwu
then click on hash and it takes you to tx and you can check if its unseen p2wsh

>>16756007
Yes this is actually a more efficient way.
>>16755968
Yes just upgraded and attempting claims on stealth addresses now to see how it works.

>>16755870
Reading this makes me feel like such a brainlet. Alright, I'll try to set it up

>>16755870
I can't find this combfullui.exe file. Where is it?

>>16756273
https://github.com/natasha-otomoski/haircomb
download that as a zip, unzip it and you will have all the files needed for the combwallet.
This is the link you will use when there is new upgrades, as you can see last upgrade was 4hours ago.

https://github.com/natasha-otomoski/bitcoin
here is the files needed to run the modified qt bitcoin core full node

>>16756306
Aye, thanks. Syncing now

>>16756413
np feel free to always ask questions, here or on the btc thread. would help others in the future to learn as well

>the year is 2050: Comb is trading $1k each
did you make it?

>>16756503
it could be much much higher then 1k each. considering it will be 30years after comb was created.
Bitcoin 11 years after creation right now is worth ~7k and has a much higher max cap.
There will be only ~12mil comb, and the inflation will take hundreds of years before it is reached.

So 30 years from now we might not even have 1mil comb yet. (don't remember the math right now)

Thus price can easily be over 10k each in even 10 years. (nobody knows if this will actually take off)

The upside potential here is absolutely huge, and the downside risk is just a few satoshi that will be provably burnt and make remaining bitcoin worth more.

>>16756007
Sorry but I don't get this bit
>check if its unseen p2wsh

>>16756867
sorry i mean t
check the address to see if its bc1 or w.e. i dont know im let too. or just use explorer to check after 1 confirmation to see if yours is at top

https://blockstream.info/tx/74972f3b997101a2e80153cbfe1b74bd2985b29e817f0f268aed860b4eab3782?expand
press details you can see one of the outputs is p2wsh.
tho this is not an unseen address, as its been used over and over, and is in almost every single block.

so your looking for an address never used. and is a p2wsh output. and is the first one (an unused p2wsh) in the block.

hope that makes sense.

its a bit difficulty to navigate through explorers and find a good way of doing it. thats why i personally just do it manually.

my steps is like this.
click on most recent block.
scroll through till i see bc1 address on an output on the right side, then press details to see if its p2wsh, then check if its unseen by clicking the address, will show me how many times there has been outputs to this address.

hope that helps.

>>16756899
all clear
thanks anon

>2 weeks until syncing is complete
See you in 2 weeks then, I guess

>>16756945
congrats,
running a full bitcoin node is always a good idea in general. helps decentralize the rules of consensus.

>>16756998
Is there any way I can get some comb without a full node just to see how it is?

>>16757017
you can get comb, but you wont be able to know if you actually claimed successfully.
basically you can attempt claims without verifying it went through, unless you go into the blockchain explorers and look for it yourself and see that you were the first unseen p2wsh in the block.

also you can send it or do any of that either.

full node is needed for sending and verifying claims.

honestly bitcoin blockchain is made specifically in a way that everyone can run a full node. this is the reason the blocks have a limit. so everyone can run a node and participate in the rules of consensus.

250gb is not much for space. once its synced it takes hardly any resources.

>>16754681
>DO NOT UNDERESTIMATE THE POWER OF POSITIVE HAIRDRESSING

>>16757120
to sum up for the brainlets
To successfuly claim comb your transaction to a miner address generated through the wallet must be the first unseen p2wsh on the current block right?
each p2wsh wallet generated through the wallet is for 1 use only then, since the output wallet of the transaction must be also unseen

>>16755927
don't mind the traumatized fucktards it's a long story

>>16757492
yes i believe what you say is correct.
each p2wsh address generated throug the wallet is for 1 use only, because the output address needs to be unseen. so if you attempted to that address once and failed/ or succeeded. you must use a new address to do a new claim.

you interchanged wallet and address but i think you got the idea.

>>16757574
>you interchanged wallet and address but i think you got the idea
I did, thanks

>>16757574
the source address doesn't need to change on each claim attempt, or does it?

>>16757702
source doesnt need to change, claims go by first unseen p2wsh OUTPUT.
but your source will change because of change addresses anyways.
unless your talking about the combwallet, you can generate many stealth addresses and attempt claim on each one not needing to change your main address.

btw i just saw somebody claim
https://blockstream.info/address/bc1qrjjrtvtjxh2427hltku9ll4ls8jkjwwfhpd5e6
who is this? im curious if you are running a full node. as that is a successful claim i think.

curious if anyone has tested sending comb?
as im a bit confused on that part. ive never done it yet. anyone sent comb successfully? and has a step by step to follow? thanks

>>16757819
As source I meant the address used to send the 546 sats to the unseen mine address

>>16757876
yes you can use the same address its fine.
but the way bitcoin works is it will send the remaining bitcoin to a new change address for you. well most wallets do that if not all. thats standard practice in bitcoin

>>16757819
oh shit thats me you go ahead though anon ill do it later, i forgot to email

>>16757835
anon sent to me in a very early thread. i just have a text file of coin history and the key (i used the online wallet generator for it)
i will test when i have the node running soon

>>16758090
haha all good.