Search content
Sort by
Showing 20 of 21 results by Security Engineer
How do you feel when I get donations anyway? Go now and verify that is true. Or try to attack blockchain and reverse 16+ confirmation. You spamming everyone's profile because you are a scammer trash who running "exchange". fck you dkbit98!
What donations are you talking about exactly, pray tell? Can you present us with the receiving bitcoin address of said donations?
Do your research you asshole! While Bitcoin talk accused some people with scam others outside of BitcoinTalk did supported them. Including myself. I sent to the accused more than $90 and I still have few thousand to send them. More you people attacking them the more money I send them because they deserve it.
I did not received any donation I just playing with dkbit98. As I said I supported user humanrightsfoundation with Bitcoin and I send not a single satoshi to any of you because you are all a disgrace because of what you did with that user. Thanks for bringing him to my attention.
You are missing the formatting of your topic. Here you need to follow.
On a side note, I understand it's an open space to talk whatever you want besides we have here freedom of speech but that does not mean you come to a community and start insulting loyal forum members without even giving any reference.
Edit: Your frustrations are understandable LOL
On a side note, I understand it's an open space to talk whatever you want besides we have here freedom of speech but that does not mean you come to a community and start insulting loyal forum members without even giving any reference.
Edit: Your frustrations are understandable LOL
Quote
You are missing the formatting of your topic. Here you need to follow.
Where these maniacs followed the format you mentioned when accused the pure user humanrightsfoundation in the topic https://bitcointalk.org/index.php?topic=5179215.0 with scam?
I needed to look that user up and I see that suchmoon, foxpup, dkbit98 and others are only scamming and spamming the forum. Including my profile. What that guy did that he was defamed so badly? Since my profile tagged with that username I think the questions here are legit. I don't think the rules matter here anyway because this board is managed by a Romanian who call himself Cyrus but allowing to attack a human rights organization and its members.
WTF! 
I use this processor for years to pay my bills for the servers etc... I never had any problem with them. Seems you are just a retard who don't know how to use Bitcoin and blaming a company for this.
I use this processor for years to pay my bills for the servers etc... I never had any problem with them. Seems you are just a retard who don't know how to use Bitcoin and blaming a company for this. ⭐ Merited by hugeblack (1)
that is usually how OP_Return outputs look like, they insert a certain type of "data" into bitcoin blockchain that sometimes has a certain purpose so it starts with the same bytes. sometimes it is just concatenated bytes and sometimes it is a full script that could be run. for example someone posted this 2 days ago: https://bitcointalk.org/index.php?topic=5179450.0
other than that i don't think anybody can give you any more information unless you also post the transaction IDs.
also i don't see how you think this has anything to do with reusing k values for ECDSA (which is i assume what you meant by "repeated R"). can you explain why you think that? have you checked their signature and saw the same R being repeated?
other than that i don't think anybody can give you any more information unless you also post the transaction IDs.
also i don't see how you think this has anything to do with reusing k values for ECDSA (which is i assume what you meant by "repeated R"). can you explain why you think that? have you checked their signature and saw the same R being repeated?
I just modified the python script to scan for repeated R correctly because the old script had some limitations. This address has 30,000+ transactions to scan. At least this transactions don't have witness. (Transactions with witness always result in repeated R according to this script...to scan them properly also need to run a full segwit node[miner] to see the signatures) I will update you with my finding in an hour or so.
Reused R with Witness (just an example one of my old scan)
Code:
Address: 1757jTnwZTQtH6kdvTDA8gZzcEe9bWF5RQ
number of txs: 44
#################################################################################
........................................
#################################################################################
Resued R-Value:
d642c916dca24dd8075ef62ce889796938f56fb1aa63f334197091267232
In Input NR: 9[global increment] 2200206abe9d5b0b43f27471f4a29653600d6db5e5d698d716b8068bf49cd57e9e9c58
Resued R-Value:
9d5b0b43f27471f4a29653600d6db5e5d698d716b8068bf49cd57e9e9c58
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 98[global increment] 220020b67073a7774403ea1dc5b1f66c37869545e1257f399d5256f2b9ff9058bfcf56
Resued R-Value:
73a7774403ea1dc5b1f66c37869545e1257f399d5256f2b9ff9058bfcf56
In Input NR: 111[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 111[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 128[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 185[global increment] 22002065a1dbfdff46ac9ac584bd5a546ad9d1dc490b2eda71fd34ff172e7d634f40ce
Resued R-Value:
dbfdff46ac9ac584bd5a546ad9d1dc490b2eda71fd34ff172e7d634f40ce
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 202[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 202[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 204[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 255[global increment] 220020619e236c9dacae4ef40a703e5f2cbcbacc2deeb8a2cf132c07fd42d5b6e65146
Resued R-Value:
236c9dacae4ef40a703e5f2cbcbacc2deeb8a2cf132c07fd42d5b6e65146
number of txs: 44
#################################################################################
........................................
#################################################################################
Resued R-Value:
d642c916dca24dd8075ef62ce889796938f56fb1aa63f334197091267232
In Input NR: 9[global increment] 2200206abe9d5b0b43f27471f4a29653600d6db5e5d698d716b8068bf49cd57e9e9c58
Resued R-Value:
9d5b0b43f27471f4a29653600d6db5e5d698d716b8068bf49cd57e9e9c58
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 33[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 94[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 98[global increment] 220020b67073a7774403ea1dc5b1f66c37869545e1257f399d5256f2b9ff9058bfcf56
Resued R-Value:
73a7774403ea1dc5b1f66c37869545e1257f399d5256f2b9ff9058bfcf56
In Input NR: 111[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 111[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 128[global increment] 220020336bd0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
Resued R-Value:
d0d58152786a9b8e38e954c9f4e37307132b226046c2df5690a986dd3332
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 158[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 184[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 185[global increment] 22002065a1dbfdff46ac9ac584bd5a546ad9d1dc490b2eda71fd34ff172e7d634f40ce
Resued R-Value:
dbfdff46ac9ac584bd5a546ad9d1dc490b2eda71fd34ff172e7d634f40ce
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 194[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 196[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 198[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 202[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 202[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 204[global increment] 22002002fdac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
Resued R-Value:
ac89f28b8efff49638aa91fca25e7616b21eda3cb9cd7199107cc47f6151
In Input NR: 255[global increment] 220020619e236c9dacae4ef40a703e5f2cbcbacc2deeb8a2cf132c07fd42d5b6e65146
Resued R-Value:
236c9dacae4ef40a703e5f2cbcbacc2deeb8a2cf132c07fd42d5b6e65146
all the secrets lie in the bytes if you look under the hood!
as the other poster said these are Omni layer transactions. the way to recognize them is first their OP_Return output which you would see as a red text on blockchain.com saying "Unable to decode output address" but looking under the hood you could see the output is this:
in case you are more interested:
6f6d6e69 Omni marker
0000 version
00000000001f tether marker
0000000e45c3c500 amount = 61,300,000,000
as the other poster said these are Omni layer transactions. the way to recognize them is first their OP_Return output which you would see as a red text on blockchain.com saying "Unable to decode output address" but looking under the hood you could see the output is this:
Code:
6a146f6d6e69000000000000001f0000000e45c3c500
the initial 4 bytes being 6f6d6e69 is an indicator of Omni in case you are more interested:
6f6d6e69 Omni marker
0000 version
00000000001f tether marker
0000000e45c3c500 amount = 61,300,000,000
The transactions in question in this topic including this output: 9bf7e6a..... Not looking like Omni
How do you feel when I get donations anyway? Go now and verify that is true. Or try to attack blockchain and reverse 16+ confirmation. You spamming everyone's profile because you are a scammer trash who running "exchange". fck you dkbit98!
Foxpup and dkbit98 are scammer spammer idiots. Eat some Foxpoop you retard.
Foxpup and dkbit98 are scammer spammer idiots. Eat some Foxpoop you retard.
Roger Ver is addicted to conspiracy theories , I remember watching a debate between him and Charlie Lee and I felt so bad for Roger that he has gone way too far with his bullshit, he someway thinks that even the simple matter of mathematics (Bcash Hardfork) was somehow manipulated by what he refers to as "Core Team", while I don't disagree with everything he says, it is always safe to assume that whatever shit he says is only meant to damage Bitcoin,and he spare no effort in doing so, and here is a an example of his last post (off-topic) on a scam accusation against " Bitcoin Games"
In regards to Bitcoin Cash, it clearly has more Bitcoin-ness about it than the BTC version of Bitcoin does.
I'm addicted for scanning the entire Internet.
Super fun.... Maybe this Roger guy owns the domain BITCOINTROLL.ORG Hello,
I have noticed thousands of Null Data (OP_RETURN) Transaction and these transactions sometimes have milliseconds between them always sending the exact same amount of bitcoins which makes the transactions identical.
I have searched before for repeated R values and I think this null data transactions are very strange.
I have extracted data from these transactions but I was failed to identify what kind of string they are. I see in thousands of transactions.
As I said everything in the transaction is identical except the data which looks like this:
Transaction 1:
Data 1: kkjtdb3vja6bzo42uqe5spjqbahvowoqjkb8fzbu56ffff4ta6vr2ag74c36ezgrindxecwpx8shggyq6vk8potpkhbeya4r
Transaction 2:
Data 2: kkjtdb3vja6bzo42uqe5spjqbahvowoqjkb8fzbu56ffff6vwtuh2bzvojmmdbxk347hfo95nhzsqiopkfb6pr7zdgmqcw
As you see the half of the data is the same. It is 92 character long and the first 46 of that is always the same in every transaction.
In other words everything exactly looks the same in different transactions except the last 46 character of the unidentified string in data.
I have that feeling that this is similar to the repeated R values but maybe I'm wrong that is why I asking here.
I currently targeting the address which sent these transactions because there is 7 BTC left on that unused address.
Thank you
I have noticed thousands of Null Data (OP_RETURN) Transaction and these transactions sometimes have milliseconds between them always sending the exact same amount of bitcoins which makes the transactions identical.
I have searched before for repeated R values and I think this null data transactions are very strange.
I have extracted data from these transactions but I was failed to identify what kind of string they are. I see in thousands of transactions.
As I said everything in the transaction is identical except the data which looks like this:
Transaction 1:
Data 1: kkjtdb3vja6bzo42uqe5spjqbahvowoqjkb8fzbu56ffff4ta6vr2ag74c36ezgrindxecwpx8shggyq6vk8potpkhbeya4r
Transaction 2:
Data 2: kkjtdb3vja6bzo42uqe5spjqbahvowoqjkb8fzbu56ffff6vwtuh2bzvojmmdbxk347hfo95nhzsqiopkfb6pr7zdgmqcw
As you see the half of the data is the same. It is 92 character long and the first 46 of that is always the same in every transaction.
In other words everything exactly looks the same in different transactions except the last 46 character of the unidentified string in data.
I have that feeling that this is similar to the repeated R values but maybe I'm wrong that is why I asking here.
I currently targeting the address which sent these transactions because there is 7 BTC left on that unused address.
Thank you
Hello theymos.
I quote here two post regarding BitcoinTalk's security and I hope you will do what I recommended.
Manager can recruit people who have knowledge about it.
That is correct DroomieChikito! 
If @theymos do what I recommended to him here: https://bitcointalk.org/index.php?topic=5179950.msg52306296#msg52306296 and in PM than he never again would need to even think about that something bad happens to the server(s) of BitcoinTalk. In the current state BitcoinTalk is vulnerable. If he does what I recommended it will mitigate all types of attacks once and forever.
This topic will loose it relevance immediately: https://bitcointalk.org/index.php?topic=309785.msg3326091#msg3326091 meaning that no more bounty. Some regarding the forum and email can be still ongoing but he would need to rewrite the entire post.
Cheers!
I can't reply to your PM theymos
I'm to new here... 
I got your PGP key. I will send you what you asked. Right now I'm busy with something else. I can assure you soon you will get the response in PM or in an encrypted email.
Is this yours?
I quote here two post regarding BitcoinTalk's security and I hope you will do what I recommended.
@theymos If I'm you I would remove Google reCaptcha before a DoS hits your main server! The sitekey my boy, the sitekey... I also did some research around the SSL certificates you got from Sectigo... Later I will contact you when I decided what to do with all this.
You don't want to keep that Google reCaptcha there mainly not only because I was able to indentify your server behind cloud but you don't need that at all! Before the cloud it was useful but now you can use just one captcha... better for you.
Quick tips for mitigation: Remove Google reCaptcha and implement Argo Tunnel
You don't want to keep that Google reCaptcha there mainly not only because I was able to indentify your server behind cloud but you don't need that at all! Before the cloud it was useful but now you can use just one captcha... better for you.
Quick tips for mitigation: Remove Google reCaptcha and implement Argo Tunnel
administrator of this forum without any knowledge of programming. I have read his post from the very first one and nothing indicates he had any knowledge of programming.
Bitcointalk are Big forum have over 2.6 Million member need knowledge of management. And not necesarry know about programing. Manager can recruit people who have knowledge about it.
If @theymos do what I recommended to him here: https://bitcointalk.org/index.php?topic=5179950.msg52306296#msg52306296 and in PM than he never again would need to even think about that something bad happens to the server(s) of BitcoinTalk. In the current state BitcoinTalk is vulnerable. If he does what I recommended it will mitigate all types of attacks once and forever.
This topic will loose it relevance immediately: https://bitcointalk.org/index.php?topic=309785.msg3326091#msg3326091 meaning that no more bounty. Some regarding the forum and email can be still ongoing but he would need to rewrite the entire post.
Cheers!
I can't reply to your PM theymos
I'm to new here... I got your PGP key. I will send you what you asked. Right now I'm busy with something else. I can assure you soon you will get the response in PM or in an encrypted email.
Is this yours?
Code:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQMuBExwwKsRCADZL8C3DWzSohJv6qcrZ2r0jdhY/BhUKzs8utbpa+wbPrBztNCN
9Gxu+6PUiFVuEhpdXpCKGy2sf+CyzOTdGYJtlIykH6jdEW/PLyW5a23SKZEHvI4S
RNWZCPF9kqujRHb++mrf6t6ehiMUkFcn0aQOYMMrk/pVrdx3LmmUSgsvOvCRRWS3
vo1uNJdlnqOA7pc6sgOs7bZI32zVk4p+1QVgZ6gKAOx2ga8IBILs3KMzt72WFdF1
1W0k92T/xQ+FHf0O9nMdeN/qKRBSZn1CMoJgaG23Kj8O3K3AwEgijBD60ByvIHOL
7WjFJ8IVA/obhn/Xoa1ZD91rDYvH/18kldVXAQDTdgjwDHNd4AItspbLTMvtovK8
RxWvNiHy7nE6j/BmlQgAl02c0soZXL2VhGw0gX+gIUZY3jD2pWQSFqdUb+dXNqVI
ISjINPqD35xm7Hll4B5CSlsjz5j+gJc8xrfWw1YAjK6SJxhQcevI+wbXBqfX3pYj
MYeOgszkSHAcs5EsW03EdYQ9SlrFk+5+4hsUBp86hEb3xaqkj3a2X3cO1J3erZ2R
ScFayjr7aTCuSmdguCsslSSyn/xW+N7f0s/C4JPgnVznfw1/BpNm7gFTfKidGmlx
ib4JtrxlwuYwNRbEFsynFHA+hjHa+NyJBHdf+MUyTQ/bzpiEhxL9QXKRDBTAGVMx
f44qR07JtFfZjogEXSWt1NP2fJhMsqWyFHJq7n7Kegf+NMPvIOiVJiAKjEQ5j2+6
X+DbBcjRgKr0vNdYeP7dnGK47LPRfX3EE+dTQerawlWunPoHBRkRmDShjxxwlV1F
eTf+buj5yFCBPNCAxKsnXi1EN78iPNkTbnWgKutTDup/fKY+1MZbK/FiymMvHes0
77n0HvzVrQIRaqmk6/jPC6o8f7IuZzpmYFnyUha2v0kdX0VcJATV/AzcIIVFJc5X
YLdcpRxW7qxIvOAJqpHvxl7Gdj7oYBwvnbnU/2Hl3HWh9Lo4AjfD+KpfT/F+iMiK
A4k5geMKtdJk+BLVZYos4qCAZX6VXraTDP2lVWXYzWGP9HKuos19H4V/y/LgJGFe
pbQnTWljaGFlbCBNYXJxdWFyZHQgPG1pY2hhZWxfbStwZ3BAbW0uc3Q+iIAEExEI
ACgCGwMCHgECF4AFAkxww8QLCwkNCAwHCwoDBAIGFQgKCQsDBRYDAgEAAAoJEMZV
VpPatZHnOagBALomn7hramaFsh4W/UfP7dUIXE9BMzgGzHM5rxIkmkSHAP0SAFRV
PBjl2xMYWJWIFnzVMX6odojMv6hneChqjhCTCLQbdGhleW1vcyA8dGhleW1vcytw
Z3BAbW0uc3Q+iIAEExEIACgCGwMCHgECF4AFAkxww8QLCwkNCAwHCwoDBAIGFQgK
CQsDBRYDAgEAAAoJEMZVVpPatZHn4isBAKTwaR9MGR6lKAdS74C+8fgDalbEf4uh
6/mAVFhQYp+GAP9quUjlRyr/po10gTEKStoXOAZ9sRhrb3TlxDRf8C1BWrkCDQRW
DgiMEAgAvWIlg2CjBwhtmMgy+RoS6/HeevH0Qnz3PntfWsTqZuw4kNcu/Xk6HCmY
clN/Lqy8nn/FTaplKTAJS14J20F16nCv5fpzJKB/5i8HLpNz16xpSSPErn1whsKV
/wFCheQ/oFGcJFZvcmauB6iJ3XBvJbAQqF7+mH2ijAHVnwb7V7ANlWyqjbYxPoyb
ro69HUoRojh5MTNv/xGLIajjNH8Ckp9J2XUCWtavj4xJEIoWB3i3C/A0NVQuPGS5
1MqvhWaRvbVlrdhqAuNN1culvZpSLu1y+2vLiyLolLn70viuyH/ouoV/NRo4yFpP
yA1PXDxk+51petVxXPXbVdqvun9Y0wADBQgAmKTl1iwmUr5ncMIc13Bkj5nzF+w8
11OPZ3P98J7Cos0cIXpqLf8FgDr0xU2oPoq33i59xK0SIrj1TqjiSWC4S5YkJNEm
/hgyb+UOk2D2Xm0SKr+2BDMSREEsLhYO1vSi1O0ND1g2QgoQNQ91aMVZ92IX4V8h
++/8smxxcjLkCRc9YrzsRLeuP3PE489n8MzdYbui7vU+RJhKL7mlKKWDKxko3sVH
kmy3CBjjyp04KNAGJwpQzY8G3XmK9eRSypc71ST0ziJxFk5+DPEM8IPZGbHvCS0k
a2yf8Gp5oaCDkSKxNoAnMKcM7fTkFuekAvRKBGB/u+71anvpRCxKslc1gYh+BBgR
CAAmAhsMFiEEXms/O6lhGTxcm0Q1xlVWk9q1kecFAl1bRX0FCQzw13EACgkQxlVW
k9q1kedNhgD+Pp0ZBMuN9VUtzuIsS9gp0DiMmehOdCV99SifqH0phWEBAISGZ6Zl
bY8GhzbuuorCW/UUPHDODxiuBvHI9+/qFjDx
=39Rd
-----END PGP PUBLIC KEY BLOCK-----
mQMuBExwwKsRCADZL8C3DWzSohJv6qcrZ2r0jdhY/BhUKzs8utbpa+wbPrBztNCN
9Gxu+6PUiFVuEhpdXpCKGy2sf+CyzOTdGYJtlIykH6jdEW/PLyW5a23SKZEHvI4S
RNWZCPF9kqujRHb++mrf6t6ehiMUkFcn0aQOYMMrk/pVrdx3LmmUSgsvOvCRRWS3
vo1uNJdlnqOA7pc6sgOs7bZI32zVk4p+1QVgZ6gKAOx2ga8IBILs3KMzt72WFdF1
1W0k92T/xQ+FHf0O9nMdeN/qKRBSZn1CMoJgaG23Kj8O3K3AwEgijBD60ByvIHOL
7WjFJ8IVA/obhn/Xoa1ZD91rDYvH/18kldVXAQDTdgjwDHNd4AItspbLTMvtovK8
RxWvNiHy7nE6j/BmlQgAl02c0soZXL2VhGw0gX+gIUZY3jD2pWQSFqdUb+dXNqVI
ISjINPqD35xm7Hll4B5CSlsjz5j+gJc8xrfWw1YAjK6SJxhQcevI+wbXBqfX3pYj
MYeOgszkSHAcs5EsW03EdYQ9SlrFk+5+4hsUBp86hEb3xaqkj3a2X3cO1J3erZ2R
ScFayjr7aTCuSmdguCsslSSyn/xW+N7f0s/C4JPgnVznfw1/BpNm7gFTfKidGmlx
ib4JtrxlwuYwNRbEFsynFHA+hjHa+NyJBHdf+MUyTQ/bzpiEhxL9QXKRDBTAGVMx
f44qR07JtFfZjogEXSWt1NP2fJhMsqWyFHJq7n7Kegf+NMPvIOiVJiAKjEQ5j2+6
X+DbBcjRgKr0vNdYeP7dnGK47LPRfX3EE+dTQerawlWunPoHBRkRmDShjxxwlV1F
eTf+buj5yFCBPNCAxKsnXi1EN78iPNkTbnWgKutTDup/fKY+1MZbK/FiymMvHes0
77n0HvzVrQIRaqmk6/jPC6o8f7IuZzpmYFnyUha2v0kdX0VcJATV/AzcIIVFJc5X
YLdcpRxW7qxIvOAJqpHvxl7Gdj7oYBwvnbnU/2Hl3HWh9Lo4AjfD+KpfT/F+iMiK
A4k5geMKtdJk+BLVZYos4qCAZX6VXraTDP2lVWXYzWGP9HKuos19H4V/y/LgJGFe
pbQnTWljaGFlbCBNYXJxdWFyZHQgPG1pY2hhZWxfbStwZ3BAbW0uc3Q+iIAEExEI
ACgCGwMCHgECF4AFAkxww8QLCwkNCAwHCwoDBAIGFQgKCQsDBRYDAgEAAAoJEMZV
VpPatZHnOagBALomn7hramaFsh4W/UfP7dUIXE9BMzgGzHM5rxIkmkSHAP0SAFRV
PBjl2xMYWJWIFnzVMX6odojMv6hneChqjhCTCLQbdGhleW1vcyA8dGhleW1vcytw
Z3BAbW0uc3Q+iIAEExEIACgCGwMCHgECF4AFAkxww8QLCwkNCAwHCwoDBAIGFQgK
CQsDBRYDAgEAAAoJEMZVVpPatZHn4isBAKTwaR9MGR6lKAdS74C+8fgDalbEf4uh
6/mAVFhQYp+GAP9quUjlRyr/po10gTEKStoXOAZ9sRhrb3TlxDRf8C1BWrkCDQRW
DgiMEAgAvWIlg2CjBwhtmMgy+RoS6/HeevH0Qnz3PntfWsTqZuw4kNcu/Xk6HCmY
clN/Lqy8nn/FTaplKTAJS14J20F16nCv5fpzJKB/5i8HLpNz16xpSSPErn1whsKV
/wFCheQ/oFGcJFZvcmauB6iJ3XBvJbAQqF7+mH2ijAHVnwb7V7ANlWyqjbYxPoyb
ro69HUoRojh5MTNv/xGLIajjNH8Ckp9J2XUCWtavj4xJEIoWB3i3C/A0NVQuPGS5
1MqvhWaRvbVlrdhqAuNN1culvZpSLu1y+2vLiyLolLn70viuyH/ouoV/NRo4yFpP
yA1PXDxk+51petVxXPXbVdqvun9Y0wADBQgAmKTl1iwmUr5ncMIc13Bkj5nzF+w8
11OPZ3P98J7Cos0cIXpqLf8FgDr0xU2oPoq33i59xK0SIrj1TqjiSWC4S5YkJNEm
/hgyb+UOk2D2Xm0SKr+2BDMSREEsLhYO1vSi1O0ND1g2QgoQNQ91aMVZ92IX4V8h
++/8smxxcjLkCRc9YrzsRLeuP3PE489n8MzdYbui7vU+RJhKL7mlKKWDKxko3sVH
kmy3CBjjyp04KNAGJwpQzY8G3XmK9eRSypc71ST0ziJxFk5+DPEM8IPZGbHvCS0k
a2yf8Gp5oaCDkSKxNoAnMKcM7fTkFuekAvRKBGB/u+71anvpRCxKslc1gYh+BBgR
CAAmAhsMFiEEXms/O6lhGTxcm0Q1xlVWk9q1kecFAl1bRX0FCQzw13EACgkQxlVW
k9q1kedNhgD+Pp0ZBMuN9VUtzuIsS9gp0DiMmehOdCV99SifqH0phWEBAISGZ6Zl
bY8GhzbuuorCW/UUPHDODxiuBvHI9+/qFjDx
=39Rd
-----END PGP PUBLIC KEY BLOCK-----
He posted this link on his video description: https://bitcointalk.org/index.php?topic=93140
https://i.imgur.com/eewEwv2.png
I think he is
https://i.imgur.com/eewEwv2.png
I wonder if he's actually paranoid enough to believe that I'm secretly editing this kind of ancient history for some arcane reason (while also sending out notifications about it),
I think he is
Hacker, Tihan, Zhou, Patrick, Donald, Amir, or anyone else with access to my money, please return it to
###################
so that I can continue to effectively promote Bitcoin.
###################
so that I can continue to effectively promote Bitcoin.
Return it to me, so that I can promote free speech, human rights, animal rights, stop climate change etc... administrator of this forum without any knowledge of programming. I have read his post from the very first one and nothing indicates he had any knowledge of programming.
Bitcointalk are Big forum have over 2.6 Million member need knowledge of management. And not necesarry know about programing. Manager can recruit people who have knowledge about it.
If @theymos do what I recommended to him here: https://bitcointalk.org/index.php?topic=5179950.msg52306296#msg52306296 and in PM than he never again would need to even think about that something bad happens to the server(s) of BitcoinTalk. In the current state BitcoinTalk is vulnerable. If he does what I recommended it will mitigate all types of attacks once and forever.
This topic will loose it relevance immediately: https://bitcointalk.org/index.php?topic=309785.msg3326091#msg3326091 meaning that no more bounty. Some regarding the forum and email can be still ongoing but he would need to rewrite the entire post.
~
I was wrong about the real forum link, it's not bitcoin.org/forum but bitcoin.org/smfHere is the link to Satoshis profile: https://web.archive.org/web/20100716225740/http://bitcointalk.org/index.php?action=profile;u=3
This is from May 16, 2012, 07:10:52 AM captured just about two year after that satoshi posted the welcome.. and this capture includes PHPSESSID=82f1a05469e9dc5d2c2829e58896cb00 Congratulations! Not dangerous (by now), but hey a robot was able to capture Session IDs back in that time?
<>
You do understand the version of SMF the forum is running on is heavily modified right?
Also, if there's an actual exploit you can make use of; why not exploit it? - If it's actually useable, you can make a lot of money.
See https://bitcointalk.org/index.php?topic=309785.0
Otherwise it might be best to just shut up.
I do believe some of the responsible person know how to patch or diff.
Try to write a security.txt and publish it to https://bitcointalk.org/.well-known/security.txt similar to this: https://securitytxt.org/.well-known/security.txt
Funny that a Hungarian also was in the project called Laszlo Hanyecz. Hungarians are invented a ton of things including the Hydrogen bomb, holography, self-replicating computer programs...
Funny that you know a lot about Hungarians... but cant read or speak hungarian....
ELFOGATÓPARANCS ALAPJÁN KÖRÖZÖTT SZEMÉLY
Should we call Interpol?
You talk about a Hungarian human rights dude and it is totally off-topic. Again, you have serious problems, hallucinations, paranoia and we will see what else. I going to leave a feedback on your profile about that you only disrupting conversation. Interpol?
Call them and tell them an engineer looks suspicious on BitcoinTalk. You can also contact the U.S. Cyber Command and tell them I'm using Bitcoin to buy zerodays for attacking, manipulating the votes in the U.S. election of 2020. Tell them I'm a Russian spy with a Huawei phone
! Before to move to the bitcointalk domain, the forum with the same SMF was on bitcoin.org/forum (or something like that, if I remember correctly) . That was the first transition from sourceforge to SMF. Seems that the database was moved to the new domain so that's why you can find the posts prior to the domain registration date.
I do not have a PC around me but if you check the wayback machine you'll find all you need to know.
If you want I can check it out tomorrow
I do not have a PC around me but if you check the wayback machine you'll find all you need to know.
If you want I can check it out tomorrow
That would be great! Thanks!
Who is responsible for the security of this forum? Anyone noticed that there is an exploit for SMF 1.1.19?
Remote Memory Exfiltration Exploit
I do recommend to upgrade SMF to version 2.0.15!
Code:
SMF 2.0.15 November 19, 2017
===============================================================================
September 2017
! Fixed a minor $smcFunc bug in Search-Fulltext.php
! Fixed a saving Settings.php bools being reset bug
! Fixed a security issue (Reported by Daniel Le Gall from SCRT SA)
June 2017
-------------------------------------------------------------------------------
! Cache the admin search results in the session and avoid IE's 2083 character limit
! Fixed a Mark Board Read bug
May 2017
-------------------------------------------------------------------------------
! Fixed Proxy URLs not handling redirects properly due to case sensitivity
! Fixed SendTopic using incorrect Post data
! Fixed SSI.php having a bad login panel
! Fixed Maintenance Page having a double login button
! Fixed a minor unsigned int typo in MySQL DB
! Fixed Deprecated installer message for ftp_connection.
! Fixed a loop bug in custom search
! Fixed SM Stat collection
! Added SM Stat collection registration to the Admin Control Panel
SMF 2.0.14 May 14, 2017
===============================================================================
! Updating session handlers
! Adding HTTPS
! fetch_web_data now uses cURL, falling back to sockets
! Ported image proxy support from SMF 2.1
! Also added HTTPS for avatars
! Added a simple exception handler
! Check session while logging in
! Sanitize some fields to help guard against XSS
! Validate email addresses with PHP’s filter method
! Fix search highlighting to not mangle/expose some HTML
! Fix password acceptance when special characters were used in UTF-8;
! Correct some random logic errors in the profile area
! Use ampersands instead of semi-colons for PayPal’s return link
! Fix sending multiple MIME-Version headers in notification mail
! Fix sending multipel Content-Type headers in all requests
SMF 2.0.13 January 4, 2017
===============================================================================
! Some file versions didn't get modified in the 2.0.12 patch
! Added check and sanitization for $_REQUEST['u'] in LogInOut.php and Reminder.php
! Added check and sanitization for $_REQUEST['uid'] in Reminder.php
! Properly sanitize author's website for packages
! Added session check when uploading packages
! Added session check when copying template files from one theme to another
! The code to remove empty BBCode was sometimes breaking things (reported by @rjen; fix provided by Sesquipedalian)
! Remove hardcoded limits for safe_unserialize as it was causing cache problems
! Update the cal_max_year setting to 2030
SMF 2.0.12 July 7, 2016
===============================================================================
! Fixed word censor injection by disallowing an empty 'proper word'
! Fixed vulnerable unserialize() code by converting all instances to safe_unserialize()
! Added a more thorough safe_unserialize() function to prevent object injection
! Fixed a bug where leaving a custom profile field blank on registration that has an email mask would throw an error
! Fixed PayPal integration to comply with the new forced SSL
! Fixed a bug where notifications were sent for messages in inaccessible boards
! Fixed editor to make the editor work with Microsoft Edge
! Fixed issue where smiley popup is blank on iOS 9 devices
! Fixed WYSIWYG editor in mobile devices
! Fixed an undefined $_POST['icon'] in Sources/Post.php
! Fixed a minor bug in Login2()
! Fixed an issue where SMF doesn't recognize new domain names and considers these as invalid
! Fixed an issue where SMF would allow empty BBC
! Fixed an issue where theme variants could not be selected
! Fixed an issue where the file version of Subs-Post.php could have been 2.0.8 or 2.0.11. It will be updated to 2.0.12 in either case.
! Updated copyright year to 2016
SMF 2.0.11 September 18 2015
===============================================================================
September 2015
-------------------------------------------------------------------------------
! Security vulnerability patched (Reported by Andrea Palazzo - Truel IT)
! safe_unserialize() function added to Subs.php
! Instances of unserialize() with user-supplied data changed to safe_unserialize()
===============================================================================
September 2017
! Fixed a minor $smcFunc bug in Search-Fulltext.php
! Fixed a saving Settings.php bools being reset bug
! Fixed a security issue (Reported by Daniel Le Gall from SCRT SA)
June 2017
-------------------------------------------------------------------------------
! Cache the admin search results in the session and avoid IE's 2083 character limit
! Fixed a Mark Board Read bug
May 2017
-------------------------------------------------------------------------------
! Fixed Proxy URLs not handling redirects properly due to case sensitivity
! Fixed SendTopic using incorrect Post data
! Fixed SSI.php having a bad login panel
! Fixed Maintenance Page having a double login button
! Fixed a minor unsigned int typo in MySQL DB
! Fixed Deprecated installer message for ftp_connection.
! Fixed a loop bug in custom search
! Fixed SM Stat collection
! Added SM Stat collection registration to the Admin Control Panel
SMF 2.0.14 May 14, 2017
===============================================================================
! Updating session handlers
! Adding HTTPS
! fetch_web_data now uses cURL, falling back to sockets
! Ported image proxy support from SMF 2.1
! Also added HTTPS for avatars
! Added a simple exception handler
! Check session while logging in
! Sanitize some fields to help guard against XSS
! Validate email addresses with PHP’s filter method
! Fix search highlighting to not mangle/expose some HTML
! Fix password acceptance when special characters were used in UTF-8;
! Correct some random logic errors in the profile area
! Use ampersands instead of semi-colons for PayPal’s return link
! Fix sending multiple MIME-Version headers in notification mail
! Fix sending multipel Content-Type headers in all requests
SMF 2.0.13 January 4, 2017
===============================================================================
! Some file versions didn't get modified in the 2.0.12 patch
! Added check and sanitization for $_REQUEST['u'] in LogInOut.php and Reminder.php
! Added check and sanitization for $_REQUEST['uid'] in Reminder.php
! Properly sanitize author's website for packages
! Added session check when uploading packages
! Added session check when copying template files from one theme to another
! The code to remove empty BBCode was sometimes breaking things (reported by @rjen; fix provided by Sesquipedalian)
! Remove hardcoded limits for safe_unserialize as it was causing cache problems
! Update the cal_max_year setting to 2030
SMF 2.0.12 July 7, 2016
===============================================================================
! Fixed word censor injection by disallowing an empty 'proper word'
! Fixed vulnerable unserialize() code by converting all instances to safe_unserialize()
! Added a more thorough safe_unserialize() function to prevent object injection
! Fixed a bug where leaving a custom profile field blank on registration that has an email mask would throw an error
! Fixed PayPal integration to comply with the new forced SSL
! Fixed a bug where notifications were sent for messages in inaccessible boards
! Fixed editor to make the editor work with Microsoft Edge
! Fixed issue where smiley popup is blank on iOS 9 devices
! Fixed WYSIWYG editor in mobile devices
! Fixed an undefined $_POST['icon'] in Sources/Post.php
! Fixed a minor bug in Login2()
! Fixed an issue where SMF doesn't recognize new domain names and considers these as invalid
! Fixed an issue where SMF would allow empty BBC
! Fixed an issue where theme variants could not be selected
! Fixed an issue where the file version of Subs-Post.php could have been 2.0.8 or 2.0.11. It will be updated to 2.0.12 in either case.
! Updated copyright year to 2016
SMF 2.0.11 September 18 2015
===============================================================================
September 2015
-------------------------------------------------------------------------------
! Security vulnerability patched (Reported by Andrea Palazzo - Truel IT)
! safe_unserialize() function added to Subs.php
! Instances of unserialize() with user-supplied data changed to safe_unserialize()
Security vulnerability patched (Reported by Andrea Palazzo - Truel IT) Author of the exploit mentioned above!
Is this the human rights dude?
Do I look like a "human right dude"? Huh, Mr. Lebowski? I would be proud if someone calls me that way but unfortunately I'm just a pure engineer looking for answers around BitcoinTalk and theymos.
I joking with you dkbit98 and seriously I don't understand what are you saying. Talk English please. I'm too tired to focus on you or translate your messages. You have some serious mental problems. I started this topic to talk about BitcoinTalk and its origins. You seems only try to derail the topic with your off-topic messages.
Dude, everybody knows theymos is satoshi. Were you under a rock? That's nothing new.
We all act like he isn't because we don't want bitcoin to die so easily. If people (by people i mean normies like you) knew theymos was satoshi, they would target him and end bitcoin instantly.
We all act like he isn't because we don't want bitcoin to die so easily. If people (by people i mean normies like you) knew theymos was satoshi, they would target him and end bitcoin instantly.
End Bitcoin instantly. I don't think so at all. Just is sick that afraid to come forward and say hey "I invented and others helped me to kickstart the greatest thing happened to humanity in this century" Bitcoin. We just going to wait until he dies? Is he going to wait until the last breath?
Oh no... let me grab my human gear and run as fast as human can run
humanrightsfoundation headcutter Ik.A. for free Security Engineer is comming
Are you taken some drug which has side effects in your brain?
At age 19 Theymos was already Administrator of this forum?
https://web.archive.org/web/20110520012200/http://forum.bitcoin.org/index.php?action=profile;u=35 Seems very surreal that sirius and Gavin Andresen just for fun made him Admin and later owner of this forum if he is not satoshi. Again, I believe he is satoshi. He was also used Windows (like satoshi). I think that Theymos reached out to sirius and Gavin Andresen for help. Funny that a Hungarian also was in the project called Laszlo Hanyecz. Hungarians are invented a ton of things including the Hydrogen bomb, holography, self-replicating computer programs... Furthermore, since the beginning I have warned over and over again that Tor is not secure against active government attacks: I wouldn't be found dead running one of these sites.
Can you show me one of these warnings? I'm interested to see what you mean by active government attacks.
If you have any access to the DNS of BitcoinTalk.org than sing the DNS. I recommend algorithm 14 (ECDSAP384SHA384) RFC 6605. I assume Theymos that you have good knowledge about cryptography and you love ECDSA
I use mobile so I can not edit the quote, but there are what you asked for, inside the quote.
One more post for the thread, on the access of theymos to [Suspicious link removed] DNS.
Please add.
theymos is one of three admins, in 2011
Please add.
Of course not, do you really need to ask?
- I was made a forum admin in 2011, after Satoshi left. (Silk Road also appeared after Satoshi left.) I didn't have any special access to bitcoin.org until around 2013, and in fact I didn't even have any access to the bitcointalk.org DNS until 2013.
- I've never bought or sold anything on Silk Road, Hydra or similar sites; nor did I have anything whatsoever to do with their operation; nor AFAIK did I even have interactions with anyone involved in running these sites. While I am opposed to drug laws, I have never used illicit drugs, and in fact I also abstain from alcohol & nicotine. Furthermore, since the beginning I have warned over and over again that Tor is not secure against active government attacks: I wouldn't be found dead running one of these sites.
- I never had any interaction with CSW. I don't have any keys related to CSW's (probably fictitious) SSS thing.
CSW's whole shtick is to just lie constantly. He's so brazen about it that some people think, "there must be some truth there," but really it's 100% nonsense.
I admit I was a little tempted to troll the world by roleplaying CSW's allegations as totally true...
- I was made a forum admin in 2011, after Satoshi left. (Silk Road also appeared after Satoshi left.) I didn't have any special access to bitcoin.org until around 2013, and in fact I didn't even have any access to the bitcointalk.org DNS until 2013.
- I've never bought or sold anything on Silk Road, Hydra or similar sites; nor did I have anything whatsoever to do with their operation; nor AFAIK did I even have interactions with anyone involved in running these sites. While I am opposed to drug laws, I have never used illicit drugs, and in fact I also abstain from alcohol & nicotine. Furthermore, since the beginning I have warned over and over again that Tor is not secure against active government attacks: I wouldn't be found dead running one of these sites.
- I never had any interaction with CSW. I don't have any keys related to CSW's (probably fictitious) SSS thing.
CSW's whole shtick is to just lie constantly. He's so brazen about it that some people think, "there must be some truth there," but really it's 100% nonsense.
I admit I was a little tempted to troll the world by roleplaying CSW's allegations as totally true...
theymos is one of three admins, in 2011
The active administrators are currently:
theymos (me)
Gavin Andresen
sirius
Sirius runs the server.
theymos (me)
Gavin Andresen
sirius
Sirius runs the server.
If this true than explain how can Theymos made administrator of this forum without any knowledge of programming. I have read his post from the very first one and nothing indicates he had any knowledge of programming.
Gavin Andresen and sirius are extremely good programmers according to my knowledge while Theymos is not. Seems to me Theymos himself is Satoshi Nakamoto under a different nick which would explain how sirius and Gavin Andresen allowed him to become the owner of the forum. On archive.org I don't see that the forum is existed on forum.bitcoin.org in 2009 or 2010.
I going to refer this topic to Wikipedia and removing from there that this forum started by Satoshi Nakamoto because it is not. The domain most certainly registered by Theymos himself and the forum is moved from another domain to bitcointalk.org.
BitcoinTesting.org is registered a few months after BitcoinTalk.org by a developer.
I requesting here to tell me under which domain the forum was available when satoshi allegedly posted the first post mentioned above, because he not posted to BitcoinTalk.org that is sure.
BitcoinTesting.org is registered a few months after BitcoinTalk.org by a developer.
Code:
Domain Name: BITCOINTESTING.ORG
Registry Domain ID: D163363722-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-08-20T11:44:14Z
Creation Date: 2011-09-19T15:48:07Z
Registry Domain ID: D163363722-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-08-20T11:44:14Z
Creation Date: 2011-09-19T15:48:07Z
I requesting here to tell me under which domain the forum was available when satoshi allegedly posted the first post mentioned above, because he not posted to BitcoinTalk.org that is sure.
Exactly this is why I started to have doubt. https://bitcointalk.org/index.php?topic=5.msg28#msg28 is dating November 22, 2009, 06:04:28 PM BitcoinFX and sirius commented on that post before the domain name BitcoinTalk.org is registered.
The third comment is posted in reply to satoshi by PrintCoins on December 28, 2011 after that the BitcoinTalk.org domain is registered.
Theymos have the user ID 35 and he registered in 2010 February.
Does this make any sense? Seems to me this forum is not started by Satoshi Nakamoto at all.
I would like to hear from Theymos regarding this concerns.
Code:
Domain Name: BITCOINTALK.ORG
Registry Domain ID: D162601474-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2018-09-25T13:25:17Z
Creation Date: 2011-06-24T05:19:00Z
Registry Domain ID: D162601474-LROR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2018-09-25T13:25:17Z
Creation Date: 2011-06-24T05:19:00Z
The third comment is posted in reply to satoshi by PrintCoins on December 28, 2011 after that the BitcoinTalk.org domain is registered.
Theymos have the user ID 35 and he registered in 2010 February.
Does this make any sense? Seems to me this forum is not started by Satoshi Nakamoto at all.
I would like to hear from Theymos regarding this concerns.