I can't go around blaming a single person... It was the whole of society, millions if people ganging up on me
 |
|
|
|
If you actually used your eyeballs I didn’t ask for $1000
If you had actually used your eyeballs, maybe you would have found one of the sticky threads at the top of this sub board and learned a thing or two before making a fool of yourself. |
|
|
|
Will pay in the next few days if this is fine?
No worries. Draft time sucks for me as a European, but I guess I'll just accept it.
Most of us are indifferent, we can make an adjustment if you have a suggestion. |
|
|
|
Welcome to the NFL Pick-Em Prediction Pool Discussion Thread. For signup information please see here: https://bitcointalk.org/index.php?topic=5507483.0Thanks to Sportsbet.io for sponsoring our competition for the 2024 season. The pool will use the Sleeper.com app to place your weekly predictions which start on Thursday night of opening weekend. The contest will extend through the NFL season and post-season, culminating with the Super Bowl. Sleeper makes entering your predictions very simple, and doesn't take more than a few minutes. The rules to play are simple; pick the teams that you think will beat the spread prediction for that week's matchup. Picking against the spread is a little more complex than simply picking the winner, and adds to the challenge. Predictions will be made for all NFL weekly matches, up to 16 matches per week. At the end of the contest, the participant with the most points (i.e. highest number of accurate predictions) wins the competition. The number of winners will be determined by the number of participants. |
|
|
|
|
Total prize pool tally:
0.02BTC and 2000 USDT
|
|
|
|
Announcing the NFL Pick-Em Prediction Pool.
Sponsored by Sportsbet.io
Predict the results of the weekly NFL (American football) matches for a chance to win a portion of the prize pool.
If you've ever been curious about American football, this is a great way to join the discussion and learn about the game.
I hope you'll join us for the fun. The pool will use the Sleeper.com app to place your weekly predictions which start on September 5th 2024, and will extend through the NFL season and post-season, culminating with the Super Bowl on February 9th, 2025.  Sleeper makes entering your predictions very simple, and doesn't take more than a few minutes. The rules to play are simple; pick the teams that you think will beat the spread prediction for that week's matchup. Picking against the spread is a little more complex than simply picking the winner, and adds to the challenge. Predictions will be made for all NFL weekly matches, up to 16 matches per week. At the end of the contest, the participant with the most points (i.e. highest number of accurate predictions) wins the competition. The number of winners will be determined by the number of participants. Discussion thread here: https://bitcointalk.org/index.php?topic=5507486.0
How to participate
To participate send your payment to the address provided below, and send me a PM with your transaction ID.
Once your payment has 1 confirmation on the blockchain I will send you the invite link to the pool.
Anyone is welcome, and everyone is encouraged to participate.
Please register early to get the best opportunity to win.
Registration will be closed before the start of the NFL's third week, 8:15pm Eastern Time (USA) Thursday September 19th, 2024.
Payment Details Entry Fee 0.5m BTC-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
DireWolfM14's escrow address for the 2024 BitcoinTalk.org NFL Pick-Em-Pool
bc1qnh0dxaj7r0s2frnxs0w7j73m6e8n6swltl8lrt
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE5uCk8qpATL256qefg7ozyN3KpUcFAmbNUAUACgkQg7ozyN3K
pUez8RAAmuhVAnLCTnOcP4C/WV6UFn+pEgVEqK3QaNfUzEdQTSamzYU/EdftWMuh
FbdYspyXIS0DKpEUdmHtZB1UcU7E5dr585Y9kcQEVNz8mj7AHrqxDx8VMxnaimdM
U1UuJHy755Tm4qaF7huhbAa/xA+J9Hsgl5S+s4yeEVsp4wYAjwEmRf9cT/rk7kRd
2p2tyYf4VI7Z8zrxBR7Uh2/ehUGOImPE/e9ySzAYQo46dLTQhomUkbC8A7E+jcI0
9zniG0XYCi/1vi25HI4RN8hADIUV0S2RW9K8ICAZZO9snbLo7aG5fz8jzrrDc3hu
UVy5DIYes9asYi6ZjimaYShdc77XoDKPsqCq7QibzR1hesc1hVJt1pgyX2CUn0SD
dPHIdM2Vw7HzbRcqsX9kAGW5R6uz1pGyTi/UYyWR/eWSKAalXlWszV0a7XnnOV6G
tlEaBWGGICjPBfUoTT1CAolSRCt+wXfRW4bJc+DAgW61CqNPk2IiwuTIRBJ4JUmT
aSCKjfs/E0/1GHOiJNlkK4ONZMEG8jiuM307bAhb9jsv7sRYRz8v0FyFrrY5hXqw
uH0149vcb1kklOICqcsnJRUfJQQm6siLK023dkDebq+iK1c0VUrG8vZ6N6bkvNPx
Iqf4Muxr99fXQJu+XlgOaZuOf1kMn4RJHGRuqz3hzVplMuGtECU=
=f7pw
-----END PGP SIGNATURE-----
PGP Fingerprint: 7EA88068A66DFBCC7CACBBEBE2E0A3A7EAB3CEA5 |
|
|
|
my mocks I would get best results when drafting first or last... as opposed to e.g. 5th. Might have something to do with getting two picks in a row, not sure. Or just a coinkidinky.
I don't think it's a coincidence, the mid picks are hard. It's also worth noting that the automated mock drafts on Sleeper seem to generate inaccurate results. I've done a few over the last few days on Sleeper and I often get pretty good players to choose from in the first two or three rounds, but when I try against real people in Yahoo's mock drafts the picks I want are usually taken. I didn't do any mock drafts last year, and I'm not sure if they really help that much. I think putting together a list of players you want to take, and focusing on using your higher picks for key positions is the better strategy. In the past I would priorities RBs for the first two picks just because they can make or break a team. There are only handful of really special RBs in the league from FF perspective, so getting the best one you can early on is a good strategy. But you also have to be willing to break from that strategy if someone really special is available. For example; last year Tyreek Hill was available so I used my first pick on him because... well, reasons. |
|
|
|
So everyone OK for next Saturday 8/31 9 pm EST ?
Works for me. |
|
|
|
 I was expecting a rickroll, but this is just as good.
|
|
|
|
The individual could be seriously ill or going through a difficult time; I read he contacted COVID and his life hasn't been easy since (I can't remember where I saw it).
This drama began long before Covid was a thing. I remember considering applying for the BitVest signature campaign in my early days as a forum user because it was one of the few for which a new account would qualify. Reports of slow payments and ignored complaints started in late 2018 or early 2019. At first there was another forum member that was managing the campaign for lightlord, who was erroneously being blamed, not recalling who that was at the moment. This has been going on for nearly six years now. It's obvious that lightlord should hand over treasury duties to someone else if he wants to keep the advertisement campaign operational. |
|
|
|
|
Forsyth Jones brings up a decent strategy, but to differ a bit from his suggestion you could just use GnuPG to encrypt a text file with the seed phrase in it, and store the encrypted file on a cloud server until you reach your destination. You could also encrypt a passphrase the same way and store it in a different way, such as send it to yourself in a email that's operated by company other than the cloud service, or yet another cloud provider.
That way all you have to remember is the password for your PGP key, and you have nothing on your person or in your luggage that suggests you own bitcoin.
I would rather trust an open source solution such as GPG/PGP than a third party software or an entire OS on a USB stick, and again you wouldn't have anything with you that could prompt questions.
|
|
|
|
I know what I saw,
No, you don't. You're an incomprehensible fool, and incomprehensible fools have a hard time comprehending simple things. The only ban that can be lifted by paying (a very small fee) is the "evil ip" ban. It's only applicable to new accounts that register using tor or vpn, and it's intended to prevent spammers and scammers from creating multiple accounts. Every once in a while it may flag an account that registered through an IP from a location that's notoriously used by previously banned accounts. Once you get banned on this forum you're banned for life, and so are all your alt accounts. There's no way to pay to lift that ban. I did this back in 2015, but I wanted to update it. I used exactly the same mapping code as last time. When someone is banned, their IP and some of their neighboring IPs receive evil points. Here I've created a map of the IPv4 Internet according to evil points. Currently, IPv6 is mapped into the 240.0.0/4 range, which is the large square taking up the top-right sixteenth of the chart. (I'm not sure yet whether IPv6 is actually disproportionately evil, or if I'm just cramming too many people into that address-space. Probably the latter is at least something of a factor, since 9% of traffic is IPv6 but 6% of this address-space is IPv6.) Here's the image (zoom in): https://bitcointalk.org/banmap201805.pngFor comparison, here's the one from 2015: https://bitcointalk.org/banmap201510.pngEach pixel is a /24 address block (ie. each pixel represents 256 IP addresses). The colors are: █ Zero or nearly zero evil █ A small amount of evil █ More █ More █ At this point you actually have to pay if you register an account in this block █ More █ More █ More █ Pretty high █ A ton of evil, more than anyone is likely to pay This is per block, so a single IP address could have an evil score requiring payment while its block still shows up as black here. A colored pixel indicates the evil score of a typical IP in that block. Addresses are laid out in the standard way. So you can for example cross-reference with these maps: https://ant.isi.edu/address/A /24 should almost never uniquely identify someone, but to be safe I randomly added, removed, and modified some of this data for plausible deniability. |
|
|
|
Narrator 1: you can ask your mates
Narrator 2: you can ask family members
Narrator 3: you can ask the bank for
Narrator 4: you can earn so much
Narrator 5: It is also fraud
You could have spared your self since you already know the drill from first 4 times you've asked and been ridiculed. |
|
|
|
As for confiscating cups of noodles, that doesn't surprise me at all; they're a notorious way of hiding C4 (plastic) explosive in a seemingly innocent looking package. This was upon arrival, so the C4 argument doesn't matter. Someone just wanted a free meal. At the risk of further derailing this conversion, your argument assumes that militants only target the method of transportation and not some building or person at the destination. The specific circumstance that you witnessed might be as you described it, merely someone looking for a free meal. Many years ago during one trip into the West Bank with my kids, crossing in from Jordan, we were detained by Israeli customs because we had packed my son's intubator into his bag. It's an implement for administering albuterol treatments incase of an asthma attack. We had reached our destination, but there was still a risk the machine would be confiscated by customs. Luckily one of the customs officials recognized it for what it was, and even better we didn't need it on that trip. |
|
|
|
I doubt that most customs officials are looking for evidence of bitcoin these days. That may change in the future, but for now I think Poker Player might be overthinking the issue. Depending on the country, I'd be more concerned about unlawful searches. I've been to countries where anything of value (up to cup noodles) gets "confiscated". You don't want those people to suspect you own Bitcoin. I didn't think of that, but very true. As for confiscating cups of noodles, that doesn't surprise me at all; they're a notorious way of hiding C4 (plastic) explosive in a seemingly innocent looking package. If you value your cups of sodium as much as I do, eat them before you arrive at your destination. |
|
|
|
The hdseed=1 thats found in the wallet dump is the seed that the xpriv is derived from right?
That's correct. Also, ABCbits reminded me; the master private keys of new wallets can be exported by using listdescriptors true. The keys displayed by that command are the ones from which all keys are derived. listdescriptors ( private )
List descriptors imported into a descriptor-enabled wallet.
Arguments:
1. private (boolean, optional, default=false) Show private descriptors.
Result:
{ (json object)
"wallet_name" : "str", (string) Name of wallet this operation was performed on
"descriptors" : [ (json array) Array of descriptor objects (sorted by descriptor string representation)
{ (json object)
"desc" : "str", (string) Descriptor string representation
"timestamp" : n, (numeric) The creation time of the descriptor
"active" : true|false, (boolean) Whether this descriptor is currently used to generate new addresses
"internal" : true|false, (boolean, optional) True if this descriptor is used to generate change addresses. False if this descriptor is used to generate receiving addresses; defined only for active descriptors
"range" : [ (json array, optional) Defined only for ranged descriptors
n, (numeric) Range start inclusive
n (numeric) Range end inclusive
],
"next" : n, (numeric, optional) Same as next_index field. Kept for compatibility reason.
"next_index" : n (numeric, optional) The next index to generate addresses from; defined only for ranged descriptors
},
...
]
}
Examples:
> bitcoin-cli listdescriptors
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "listdescriptors", "params": []}' -H 'content-type: text/plain;' http://127.0.0.1:8332/
> bitcoin-cli listdescriptors true
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "listdescriptors", "params": [true]}' -H 'content-type: text/plain;' http://127.0.0.1:8332/
|
|
|
|
Yes im in the US but the issue is that i have limited internet speed and also limited mb per month..  I could copy the block chain onto the drive before I send it to you, that's not a big deal. I'm traveling at the moment and won't be home until Tuesday, but let me know if you want it and I'll get started on it next week. I managed to use the console without downloading the whole blockchain so thats fantastic.
Yeah, as long as your pruned node is synced with the wallet you don't need the whole blockchain. I also found out that the dumpwallet in bitcoin console is only for legacy wallets. Is there any built in function to dump sql wallet?
Unfortunately (or fortunately, depending on your take on the issue,) no. That feature was disabled for new wallets from a few versions back (taproot implementation, I think.) Using hdseeds to back up and restore wallets wasn't a great idea to begin with, so the dumpwallet command was obsoleted. Here's an explanation by one of the bitcoin developers as to why it wasn't a good thing to do: https://bitcointalk.org/index.php?topic=5215266.msg53539363#msg53539363You can still dump the private key of any specific addresses, though. dumpprivkey "address"
Reveals the private key corresponding to 'address'.
Then the importprivkey can be used with this output
Note: This command is only compatible with legacy wallets.
Arguments:
1. address (string, required) The bitcoin address for the private key
Result:
"str" (string) The private key
Examples:
> bitcoin-cli dumpprivkey "myaddress"
> bitcoin-cli importprivkey "mykey"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "dumpprivkey", "params": ["myaddress"]}' -H 'content-type: text/plain;' http://127.0.0.1:8332/
(code -1)
|
|
|
|
|
Show Posts
