In Adobe Flash Player versions newer than 32.0.0.344 they added a "Timebomb" for the EOL.
the player would refuse to run any custom flash content after 12/01/2021,
instead it would just show this
So knowing this, Lets crack it!
I acturally started looking into this before the 12/01/2021 hit, but only recently did i acturally discover a way to bypass the killswitch
(also- im aware i was not the first to do this, but i still did do it)
A description of known problems in Satoshi Nakamoto's paper, "Bitcoin: A Peer-to-Peer Electronic Cash System", as well as notes on terminology changes and how Bitcoin's implementation differs from that described in the paper.
The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power.
| #### Copy over block data to your Dojo #### | |
| ## Written for use with Ubuntu Desktop 18.04 LTS ## | |
| ## On your machine running Dojo, open 2 terminals, we'll call them [terminal A] & [terminal Doc] | |
| ## In [terminal A] Check the size of your .bitcoin directory | |
| $ df -hf ~/.bitcoin | |
| ## In [terminal A] Ensure you have enough hard drive space to copy over the content to the container. |
| ###### User friendly interface script for interaction with ./dojo [command] ###### | |
| ## Written for use with Ubuntu Desktop 18.04 LTS ## | |
| This script is setup to run locally from the machin that your Dojo is installed on, but if you wanted to use it via SSH | |
| there is a write up below the script on how to set that up. | |
| ## Open a terminal | |
| $ mkdir scripts | |
| $ cd scripts && touch control_dojo.sh |
| All credit goes to Mark Engelberg (https://github.com/Engelberg) for figuring this out! | |
| His original writeup can be found at: | |
| https://gist.github.com/Engelberg/aac9da2f27b723683982d187bd4d5ea4 | |
| Thought I'd just write more of a follow along tutorial for the less technical | |
| ## Written for use with Ubuntu Desktop 18.04 LTS ## | |
| ## Stop your Dojo |
| ## Getting LND working with Dojo | |
| ## Start Dojo | |
| $ cd /path/to/docker/my-dojo/ && sudo ./dojo.sh start | |
| ## Login to the bitcoind docker container as root | |
| $ sudo docker exec -u root -it bitcoind /bin/bash | |
| ## Update and install a text editor | |
| $ apt-get update && apt-get install nano |
list of links for quick copypasting when debating on forums, also useful as a reading list
this was posted on reddit, link is https://www.reddit.com/r/Bitcoin/comments/7mh8c2/long_live_decentralized_bitcoin_a_reading_list/
a trip to the moon requires a rocket with multiple stages by gmaxwell https://www.reddit.com/r/Bitcoin/comments/438hx0/a_trip_to_the_moon_requires_a_rocket_with/
bram cohen, creator of bittorrent, argues against a hard fork to a larger block size
Today (April 16th 2019 at noon) the first major clues to discover key #1 was set to be released in a few cities. A QR code with the words 'orbital' were found at these locations and looked like this: (https://imgur.com/a/6rNmz7T). If you read the QR code with your phone you will be directed to this url: https://satoshistreasure.xyz/k1
At this URL you are prompted to input a passphrase to decrypt the first shard. An obvious first guess was to try the word 'orbital' from the QR code. Not suprisingly this worked! This reveals a congratulations page and presents the first key shard:
ST-0001-a36e904f9431ff6b18079881a20af2b3403b86b4a6bace5f3a6a47e945b95cce937c415bedaad6c86bb86b59f0b1d137442537a8.
Now, we were supposed to wait until April 17th to get clues from the other cities for keys #2 and #3 but that wouldn't stop me from digging around with all the new information we had. All that time "playing" notpron (http://notpron.org/notpron/) years ago was going to help me here.
The first thing I noticed was
| @echo off | |
| rem choco install -y openssl.light | |
| rem choco install -y wget | |
| rem choco install -y cygwin | |
| rem tail -c +257 trezor.signed.bin | sha256sum | |
| rem https://crt.sh/?q=26AFA022ADC5EE7E41A5226C1DE336D438F1AD0F | |
| setlocal | |
| set tail=%ChocolateyToolsLocation%\cygwin\bin\tail.exe | |
| set sha256sum=%ChocolateyToolsLocation%\cygwin\bin\sha256sum.exe | |
| set openssl="%ProgramFiles%\OpenSSL\bin\openssl.exe" |
| So, the way this goes is I post my AVR code, then I post what the HTC Vive does. | |
| The output is: POST 0: (# of bytes) (IMU Timecode MSBs) (All raw light data) | |
| (All raw light data ends with [3 bytes, LSB timecode] [OTA CRC (probably ignore)]) | |
| Events (TIME): (LED CODE 1)/(TIME CODE 1/TIMECODE 2)/(LED CODE 2)/(TIME CODE 3/TIMECODE 4)... | |
| //NOTICE: The funky encoding of the numbers, and the fact that paramters are read from the end of the data going forward. | |
| //We know we're done when the # of parameters read is (# of bytes left*2)-1 |
