/biz/ - Business & Finance

>>16286553
>poo in loo
>female
>russian alias
DOA

>>16286553
Damn, am I tripping??

natasha otomoski

satoshi nakamoto

how many to make it?

Redpill me on COMB

>>16286592
yes mr sanjeevi her wrote the coding to BTC in c++ at age 15 XD

GET FUCKING REAL YOU FAGGOTS

MINISTER YOU OTOMOSKI CHAN

will anyone sell me 2 COMB for 50 $??

>>16287022
Sure send me 50$ btc to this address
3LKV3pJWKJNFzYN3s3zxyR7J7acjASbjhb
Give me a comb address. I will send you 10comb and proof that i funded the 21 addresses to send it.
Currently cost me less then 1$ Per claim on average.

are you in Discord? There can we talk about the details.

>>16287117
sure whats your discord

Make a telegram not discord bros

>anonymomity

>>16287072
How does it cost you less than $1?
Can you post a successful claim tx?

>>16287153
don't use either, just made a temporary discord for this
doesn't telegram ask for phone number, how would it be better

>>16287166
That was done on purpose

>>16287166
>plebbit/user/AnonyMomity
which one of you autists did this

>>16287184
Whats the discord?

What did he mean by this
>still not 100% sure how it exactly works, since ive noticed times when i used low sat/byte and i was really far down in the block, and had many other tx's to bc1 addresses that were also p2swh txs but i still got the claim. edit: meaning other txs payed higher fee and were ontop of mine and also to bc1 addresses and also p2swh but i still got the claim

>>16287876
oh that's me.
still figuring things out here

>>16287904
based, same here
btw the list for the 3000 successful claims was posted on here. type justpaste in the archive and they're in some earlier comb thread

i think the reason could be that some miners don't sort by fee. at least that's what i gathered from reading the old threads on here about it. seems like the dev rec'd to use a high fee because some miners do sort by fee, guess that means some dont

>>16287945
actually i think its most likely reused p2wsh.
after reading whitepaper again, it says it has to be an unseen p2wsh.
so most likely anytime i claimed when other txs with bc1 addresses were higher up, had to have been addresses that were not unseen. but im waiting on my full sync again to test and see.
thats what my hypothesis is atm.

have you claimed any yet successfully? are you fully synced?

dev didnt req high fees for claims, the only requirement is the first unseen p2wsh tx in the block.
and since miners are the ones that sort by fee, thats what gives higher fee a better chance to be first or higher up

>>16287945
cant find the pastebin can u link it

>>16287968
>actually i think its most likely reused p2wsh.
so does that just mean addresses that haven't been used before?
and no im the anon in the ann thread, cant sync but i attempted to claim offline just by sending to wallets i generated just dont know if it actually worked yet. how many have you claimed so far?

from the other thread:
justpaste dot it/3pghk

>>16288068
wow alot of these arent even actual claims with 546 sat tx.
wonder if they are still able to move them?

i dont remember how many i claimed and my node still syncing, 86% now, but i think i got atleast 15 successful claims.

>>16288618
yep i asked in a previous thread. those are probably not comb claims so that comb will be burned since they cant access it
man i'm pissed i can't sync. if this takes off in a big way i might necc desu

>>16288652
why you cant sync? natasha just recently said that prune node is supported.

im using an old laptop myself, if i didnt delete the commits.db and saved it properly i wouldnt have to resync. and the resync is almost done even tho i started it today.

that means full sync with blockchain takes less then 12hours depending on hardware.

and downloading 250gig for the full chain can also take like a day or two depending on your internet. you can always go to a datacenter workspace and pay 5$ for the day and use their highspeed to download it if you really need.

>>16288677
im using old thinkpad and it's saying 2~ weeks, i will eventually sync it just might take a while and i don't want to attempt to claim more without seeing if previous attempts were successful, and to not end up paying $5 per claim attempt like i was doing.

i tried the pruning method but i got error blockchain shorter than block height set (or similar) after pruneblockchain 481822 in command line - probably because i hadn't even got to that block yet with the sync due to it being so slow.
at first i thought maybe the wallet was malicious or something because when i left it on over night my laptop had restarted lol but its just the shitty laptop man

im gonna try claim some more after it eventually syncs

>>16288809
u have no desktop? or better laptop?
thankfully i have an old "gamer laptop" that i dont use, decided to make it full node.

ive had successful claims with as little as 25-30 sat/byte plus the 546, so total was around/under 10k sats. tho not always were they successful

>>16288828
no but appreciate the help anyway ill figure it out

in total i attempted to claim around 80 times but the first 40 or so were to the same addresses lol. but at least 35 after that seem like they could be good, paid high fees too
in an older thread some anon said there were only 350 in circulation

i will claim some more with lower fees soon

fully synced, will show proof of claims soon

>If the Bitcoin block contains no P2WSH output, no combbase is awarded.
>If the Bitcoin block contains no previously unseen P2WSH output, no combbase is awarded.
>If the Bitcoin block contains some previously unseen P2WSH output, the first previously unseen P2WSH output gets the reward.

So unseen P2WSH output just means an unseen public key?

>>16289542
not sure if those are the same thing.
pay to witness script hash, is p2wsh
tho in this context it might be the same as an unseen bc1 address.
ive noticed there is shorter bc1 addresses and longer ones are the ones that the wallet gives for burn addresses.
so not sure if they are the same thing or something different is going on there.

you know, just reading the whitepaper and ann thread again..
>Currently a good way is to claim it using an unrelated Bitcoin or haircomb transaction that you are going to do anyways. It is a no-brainer to add the first destination of 546 sats to participate in the COMB lottery. If everyone was doing this the COMB claiming network would be very decentralized.
>Exchanges can also claim COMB.
>Child pays for parent transactions are also an option. Claimer creates many lower fees transactions that depend on each other. To pocket a good fee, miner has to include several in the sequence. This produces a burst of transactions maybe giving an increased chance that one of the burst transactions wins the reward.
yeah I'm thinking we're gonna make it

>>16290048
>based
>exhangepilled

OOOOOOOOH FUCKKKK I'M COMBINGGGGGGGGGGGGGGGGGG

It's real sad to know some retard will fall for your organized shilling. No matter your screech responses crying how is it a scam, one only has to look at how worthless the banner and white paper are.

Fall for it and you deserve it. I will not be reading your replies, I'm already out of the thread.

>>16290569
literally anyone that is making a p2wsh tx has already entered a chance to claim. weather they know it or not
all they need to do is add 546 sat as the first output to tip a mine address.

>Your wallet must support segwit.
If you claimed from a legacy address (to send to the bc1 claim address) does this mean it will 100% not get the claim reward?

>>16290933
in order to be able to claim the comb.
546 sat needs to be tipped to the specific bc1 mine address (which is verifiably burnt)

because this is p2wsh pubkey, it can only be made from a wallet that supports this.
https://bitcoincore.org/en/segwit_wallet_dev/

now i think i get what the previous anon was saying.
maybe it can only be from an unseen bc1 address. and only the long bc1 addresses are the ones that are able to claim.
meaning if just an unseen bc1 address. then it could still win but its unclaimable so no1 else wins that block.
or if its just a seen bc1 address then it doesnt win and only the first unseen in the block wins.
so if everyone just added into every new bc1 address the first output of 546sats to the burn address. they can automatically be attempting to claim.

since alot of exchanges and payment processors already are using this. why not just add a simple 546 tx to their multiple output tx's anyways and attempt to win the reward.