OpenLLM-France/wikimedia huggingface dataset:
# Radium SmartChain/Linux Mint Hack

On February 20, 2016 the Linux Mint website was hacked. The hackers were not only able to access the Mint mirrors to replace the iso files, but also got into the website and replaced the check-sums on the downloaded isos. What this means is if you downloaded their iso on the day it was hacked, even verifying the download would have returned that it was the appropriate file since the incorrect check-sum was being used for verification.

## How could this issue have been avoided?

With Radium Smart-Chain technology! With the ability to record a file's check-sum directly into the blockchain, the sha256 hash would have been forever recorded and impervious to external manipulation. This technology seeks to allow users the ability to quickly verify the integrity of open-source and shared files within a single user-friendly application as demonstrated below:
1) The first step would be done by the creator of the original file being shared. This user would record the files check-sum on the Smart-Chain during the process of making it publicly available for download.
2) The second step is done by any user wanting to download the shared file in question. Much like the first step, the user simply identifies the file through the Smart-Chain and receives a confirmation that the file is intact and unchanged if the check-sums check out.

## Additional Radium Smart-Chain Functionality and Cyber-Security Implications

Along with recording file check-sums, the SmartChain also has the ability to record text notes. What this means is the sha256 check-sum text file located at http://mirrors.kernel.org/linuxmint/stable/17.3/sha256sum.txt could have been permanently recorded with no chance of a man-in-the-middle attack being able to replace the text file from the mirror website!
With the ability to verify hashes in the SmartChain instead of relying solely on potentially compromised websites, users will not only be able to avoid infecting their machines, but they will also be able to pro-actively combat compromised files leading to a much safer inter-netting experience.
# Radium Core/Use Cases/Transmission BitTorrent Ransomware Case
## Mac users still impervious to malware? Think again.

On March 7th, the first MAC ransom-ware was discovered on a recent update to the Transmission BitTorrent Client. The malicious software was downloaded 6,500 times before it was uncovered that it was not the real file version. Apple as well as Transmission have since released the correct file update and are now assisting all of the affected community members with removing the malware.

## One-Click Verify Can Help

The Radium Smart-Chain is focusing on assisting open-source groups with securing the distribution of their software. If the Transmission software check-sums were registered on the Smart-Chain, all community members downloading the software could have utilized the One-Click Verify application to get an instant confirmation that the file was malicious.
One-Click Verify does direct comparisons of target file check-sums against the unalterable stored check-sums, which the developing organization publishes on the Radium Smart-Chain.
In this case, 6,500 users could have been spared the terror and frustration of having to remove this malware. The release article does not suggest how many users paid the ransom, but at $400 each One-Click would have been worth the small time investment for Transmission.

## Get Your Files Published!

To the Transition team or any other group reading this, contact Project Radium for details on getting your Check-sums published to the Smart-Chain.
You can read the whole article here: http://www.macrumors.com/2016/03/07/transmission-malware-downloaded-6500-times/
# Radium SmartChain/Elections
## How to vote

Step 1: Select the SmartChain identity with which you want to create your SmartChain election with. You can find your identities under the My Identities tab.
Step 2: Under the voting tab double click the election you want to vote on.
Step 3: In the dialog box, right click the entry you would like to cast and click “Vote for Selected Candidate”.
Step 4: Confirm your vote by clicking “Cast Vote”.
Step 5: Once you’ve completed these steps a pop-up will appear with the blockchain fee to be paid and details concerning your election. Hit “Ok” and wait 4 blocks for the election to confirm. You have now voted in a Radium SmartChain election!

## How to setup a new election

Step 1: Select the SmartChain identity with which you want to create your SmartChain election with. You can find your identities under the My Identities tab.
Step 2: Under the voting tab click the button with the label “Create An Election”.
Step 3: In the dialog box which appears please enter the title (i.e. question), duration and description of your election.
Step 4: Enter candidate names (i.e. your poll choices) and click the “Add Candidate” button to add the name to your list of candidates.
Step 5: Once you’ve completed these steps click the “Create” button. A pop-up will appear with the blockchain fee to be paid and details concerning your election. Hit “Ok” and wait 4 blocks for the election to confirm. You now have an ongoing election on the Radium SmartChain!
# Radium SmartChain/Proof of Author

Proof of Author has uses beyond Bitcointalk but this usage scenario is intended as a Smartchain based Proof-of-Developer and uses the Project Radon Smartchain client to secure file downloads from infamous "repost trolls." Terrible Problem: OP Dev Alice posts wallet update on thread Scammer Billy quotes Alice but changes the html in her link Noob Bob downloads Billys link thinking it is Alice's release and Bobs computer becomes infected.
Low Cost Avoidance: OP Dev Alice secures the hash of her github source (likely zipped) and file download links (zipped or unzipped however theyre linked) in the Smartchain using her known registered Smartchain username. OP Dev Alice requests users wishing to run her coin wallet or program to also download the Project Radon One-Click-Verify tool and use it on any downloads posted. OP Dev Alice posts updated files whose hashes have been stored in the Smartchain. Scammer Billy quotes new links and changes the URL to an imposter. Noob Bob downloads nefarious links but runs the Project Radon Smartchain One-Click-Verify tool and notes the files do not belong to Dev Alice. Bob does not run the executables Bob also reports Scammer Billy. Crisis averted, Bobs computer remains safe.
This scenario helps people double check a file they downloaded is from who they intended it to be from. It requires no Radium client or Smartchain client to verify a file so it is easy for the end user. A prospective developer would need to run the clients and accumulate a small amount of Radon tokens to secure hashes in the Radium chain as well as the initial verification of their name.
This scenario will allow you to make sure you get Alice's file but if Alice's file is malicious the Smartchain is not responsible for the content of anything stored within.
# Radium Core/Use Cases/Linux Mint Hack

On February 20, 2016 the Linux Mint website was hacked. The hackers were not only able to access the Mint mirrors to replace the iso files, but also got into the website and replaced the check-sums on the downloaded isos. What this means is if you downloaded their iso on the day it was hacked, even verifying the download would have returned that it was the appropriate file since the incorrect check-sum was being used for verification.

## How could this issue have been avoided?

With Radium Smart-Chain technology! With the ability to record a file's check-sum directly into the blockchain, the sha256 hash would have been forever recorded and impervious to external manipulation. This technology seeks to allow users the ability to quickly verify the integrity of open-source and shared files within a single user-friendly application as demonstrated below:
1) The first step would be done by the creator of the original file being shared. This user would record the files check-sum on the Smart-Chain during the process of making it publicly available for download.
2) The second step is done by any user wanting to download the shared file in question. Much like the first step, the user simply identifies the file through the Smart-Chain and receives a confirmation that the file is intact and unchanged if the check-sums check out.

## Additional Radium Smart-Chain Functionality and Cyber-Security Implications

Along with recording file check-sums, the SmartChain also has the ability to record text notes. What this means is the sha256 check-sum text file located at http://mirrors.kernel.org/linuxmint/stable/17.3/sha256sum.txt could have been permanently recorded with no chance of a man-in-the-middle attack being able to replace the text file from the mirror website!
With the ability to verify hashes in the SmartChain instead of relying solely on potentially compromised websites, users will not only be able to avoid infecting their machines, but they will also be able to pro-actively combat compromised files leading to a much safer inter-netting experience.
# Radium SmartChain/Development History
## Stuff in the Works (updated 8/6/16)
### SmartChain 3.0

SmartChain 3.0 will be the third major release of the SmartChain, and will include the following features:
(windows only)
* Removal of Radon and Radon Decay
* Brand new XAML GUI
* Release date was on March 27th 2017

## Radium SmartChain Development history
### Phase 2.4

Public release March 30 2016
* SmartChain Radon cost adjustment
** Cost to register a username changed from 10 Radon to 5
** Cost for other operations reduced to 1 Radon per 40 bytes
* User Experience
** All new graphics
** Columns can now be re-sized, re-ordered, and sorted ascending/descending.
** Full Radium Send history now visible.
** Full Radium Decay history now visible.
** Added filtering and searching to registered user fields.
** Fully automated Radium Wallet launch.
* Performance
** Transition back-end data handling to a relational database structure.
** Added low resource usage sync.
** improved sync loop speed
* Technical
** Added Custom RPC credentials.
** Added Custom wallet data directory.
** Added wallet sync state checking.
** Added wallet connection state checking.
** Added sync queue length stats on the syncing splash page.
** Sync data and required files moved to /appdata/SmartChain

### Phase 2.3

Released Feb 2 2016
* Fixed various issues and bugs related to handling orphan blocks.
* Reduced maximum slow decay rate to to allow confirmation time.
* Fixed "disappearing user" bug, related to orphan blocks.
* Removed wallet sync checking that was causing random bugs.

### Phase 2.2

Released Jan 28 2016
* Fixed issue preventing some users from registering.
* Fixed code for displaying update warnings.

### Phase 2

Released Jan 26 2016
* NEW FUNCTION Proof of Existence: Text Notes
* NEW FUNCTION Proof of Existence: File Hashing + Verification
* NEW FUNCTION Radium Send
* NEW FUNCTION Blockchain announcements for leisure/major/critical updates
* Added session history for Radium Decay
* Multi-Threaded Sync Engine for improved sync speed
* Various minor GUI Updates and Improvements
* Various code optimizations

### Phase 1.2

Released Jan 19 2016
* SmartChain Client updated to work with re branded Radium wallet.

### Phase 1.1

Released Jan 12 2016
* Fixed incorrect display of Radium and Rad balances

### Phase 1

Released Jan 12 2016
* Phase 1 Release, and ANN posted.
# SwisTrack/Examples/Calibration

SwisTrack includes several calibration components. The purpose of all these components is the same: they convert image positions (expressed in pixels) to real-world positions (usually expressed in meters). What differs is the geometrical model that they use to do this transformation.
All calibration components implemented so far use a list of points to fit such a model. I.e. you provide the component with a list of points of which you know the image position and the real-world position:
The component then finds the model parameters that minimize the error when converting your image points to the corresponding real-world points, and subsequently uses these parameters to map image coordinates to world coordinates.
Hence, all you need to do is to come up with a list of such points. This is fairly simple and can be done in several ways:
* Semi-Automatic Calibration: This is the simplest approach and consists of placing markers at known position in your arena. On the image, you manually click on each marker.
* Automatic Calibration with a Known Pattern: This is similar to the semi-automatic calibration, except that the markers are found automatically.
* Automatic Calibration in a Sequential Fashion: Use this method if you have the possibility to move a marker to specific (precisely known) places in the arena.
For each of the methods, we provide you with a detailed description and the necessary scripts.
# SwisTrack/Developers/Setting up a development environment

If you want to implement your own components, or if you want to actively participate in the development of SwisTrack, you need to set up a development environment:
* Setting up a development environment on Linux
* Setting up a development environment on Mac OS X
* Setting up a development environment on Windows
# SwisTrack/Examples
## Getting Started

Try to get the leurre example running, which is in subversion and in the bundle released. It ships with an AVI file, so you can get it running without messing around with cameras or making it work on your video. Make sure you can use the display to see images from each stage in the pipeline.
After that, create a pipeline of your own by selecting approximately one component from each category, which usually looks something like this:
* Trigger component, usually timer trigger. Optional.
* Input component, either camera or from AVI file (for testing purposes also from image file).
* Conversion to color.
* Adaptive background subtraction.
* Thresholding.
* Binary mask, perhaps.
* Blob detection
* Calibration with TSAI
* Tracking, if desired (you get positions even without this)
Build the pipeline gradually, verifying things are working by using the display after each step. Tune the parameters to make it work well on your video, and take a look at the examples to see the best way to set things up.

## Real-World Examples

The following examples may serve as a good starting point for your application. You'll find these examples with all necessary files in the Example folder of SwisTrack.
* RobotTracking: Tracking robots with an overhead camera

## Feature Presentations and Utilities

The following examples present a feature (usually a component), and shows you how and in which setup it is used. You'll find these examples with all necessary files in the Example folder of SwisTrack.
* ParticleSimulation
* Calibration
** SemiAutomatic: Semi-Automatic Calibration
** Automatic: Automatic Calibration
** AutomaticSequential: Automatic Calibration with Sequential Images
* OutputProcessing: Templates for interfacing SwisTrack
* MultiCamera: Program to start/stop multiple cameras with a single click
* IDReaderRing: Reading circular barcodes around a blob
# SwisTrack/Developers/Setting up a development environment/Linux
## Prerequisites

You need the following programs and libraries:
* Subversion (SVN)
* Intel Open Source Computer Vision Library OpenCV
* wxWidgets
The following libraries are optional and only necessary if you want to use the corresponding cameras:
* Basler Pylon driver
* Firewire camera driver

## Ubuntu 12.04 and later

Install Subversion
Install wxWidgets:
Install OpenCV2:
Checkout the trunk of the svn repository:
Compile:
Run:

## Ubuntu 8.04

On Ubuntu 8.04, it should be enough to install the packages
* libwxgtk2.8-dev (wxWidgets)
* libhighgui-dev (OpenCV)
* libcvaux-dev (OpenCV)
Use Synaptic Packet Manager or type
on the terminal to install these packages.

## Other distributions

If your distribution does not provide a package, you can compile and install these libraries manually.

### Manually Installing OpenCV

Download the OpenCV 1.0 sources [ http://sourceforge.net/projects/opencvlibrary/files/opencv-unix/1.0/ ]and compile and install them:
For detailed installation instructions, check out the INSTALL file.
Note that the current SwisTrack Makefile expects OpenCV to be installed with the prefix /usr. If you install it elsewhere, do not forget to modify the INCL_DIRS line in the Makefile appropriately.
When installing OpenCV 1.0 in newer Ubuntu distributions you may find the following issues:
1) Error message:
To fix it, change line 133 in cxmisc.h from #elif to #else.
2) Error message:
To fix it, add #define HAVE_CAMV4L after line 24 in cvconfig.h
3) Error message:
To fix it, install libv4l-dev and link to it with the following commands:

### Manually Installing wxWidgets

Download the wxWidgets 2.8.8 sources (either wxGTK or wxAll) [ http://sourceforge.net/projects/wxwindows/files/wxAll/2.8.8/ ] and compile and install them.
You are free to change the prefix here, as SwisTrack uses 'wx-config' to locate wxWidgets.

### Installing Optional Libraries

If you have a FireWire camera, install the 1394camera driver.

### Installing OpenCV legacy packages

Depending on the opencv version installed in your system, you may also need to install the OpenCV legacy packages. In that case, run the following command:

## Library Paths

Depending on your system configuration, SwisTrack will complain about missing libraries. You may see error messages like this:
In this case, you need to set your LD_LIBRARY_PATH variable to point to the directory where these libraries are installed. If you are using a bash shell, this can be achieved as follows:
On Ubuntu 10.10 the following is required : export LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH and create a dynamic link on the cvaux libs : sudo ln -s libcvaux.so.2.1 libcvaux.so in /usr/lib/
# SwisTrack/Developers/Setting up a development environment/Mac OS X

If you have the Apple XCode Tools installed on your Mac, you can follow the guidelines for Linux (Other distributions, manual installation) for setting up your development environment. The only difference is that you have to install wxMac instead of wxGTK. Instructions for installing OpenCV on Mac are available from [Willow Garage].
SwisTrack should compile within XCode (use code/AppleXCode/SwisTrack.xcodeproj on the SVN tree) and through the make build system ("Makefile"). You can create the application with "make osxbundle" run in the directory /Code/gui.
For all you lazy OS X users: I compiled the SVN code (r1028) and statically linked against the latest versions [as of May 2015] of wxWidgets [wxCocoa] and OpenCV. That was not as straight forward as it should be.... Some notes: the components window is no longer a modal dialog, so the cancel button has no effect. When a checkbox won't tick, click in the main window first. When loading files from AVI [not true, it takes various formats...] enter the full path, the dialog doesn't work. The app will probably only work with OS X 10.10.x Yosemite. Binary.
# SwisTrack/Download and Installation
## Downloading SwisTrack

SwisTrack is under continuous development, and since it is a tool created by researchers for researchers, there is no fixed release cycle. If you wish to have the latest version of SwisTrack, get the source code via SVN as described in the section Setting up a development environment. For some systems, precompiled versions are available.

### Windows

On SourceForge, you'll find SwisTrack for Windows. If you plan on using video files, you may also want to install the K-Lite Codec Pack.
# Super Mario Bros. 3/Regional differences

Super Mario Bros. 3 has several differences in the Japanese (Famicom) version and English (NES) version. None of these are retained as differences between the Japanese and English differences of the Super Mario All-Stars port of SMB3. Both versions are either like the Japanese Famicom or like the English version, depending on the difference.
The differences are:
* The Japanese version and All-Stars version has an iris-in effect before a level starts, and then an iris-out effect after it. The English version has only an iris-in effect.
* In both the Japanese version and All-Stars port, Fire or Raccoon Mario will become small Mario after one hit. In the English version, Fire or Raccoon Mario will only go down to Super Mario.
* In the World 1 Fortress, in the room with the spiked ceiling, the Japanese version has 3 blocks after the door. The English version and All-Stars port has the wall immediately after the door.
* In the Japanese version, when the king of a world is transformed, the room has 3 columns and Mario starts out on the left. In the English version, there are 2 columns and Mario starts in the middle.
* In the Japanese version, Frog/Tanooki/Hammer Mario will have a suit fly off in response to a hit. This suit fly off was removed in the English version.
* In the Japanese version, if Mario uses a warp whistle while in the World 3 canoe, Mario and the canoe will go together into the Warp Zone and Mario can go into the water the island is inside, and he's stuck unless he uses another warp whistle. This was fixed in the English version; Mario alone will go into the Warp Zone.
* In Level 5-1, the Japanese version has a pipe that must be entered before getting to the goal panel, making an unnecessary glitch possible. In the English version, the pipe was removed and the goal panel was moved to the area where the pipe was in the Japanese version.
* When Mario has a Kuribo shoe, in the Japanese version, he will become small Mario after a hit. In the English version, Mario will lose the shoe, but remain in the same power-up condition he was in before the hit.
* In the World 8 Battleships, it is valid to swim under the battleships. In the Japanese version, if this trick is done, it is possible to get back up only with a Frog Suit or P-wing because the wall is too tall otherwise. In the English version, the upper right corner of the last battleship was removed to make it possible to get back up.
# Super Mario Bros. 3/Items/Tanooki Suit

The Tanooki Suit is one of the power-up suits in Super Mario Bros. 3 on the Famicom or the Nintendo Entertainment System gaming console.
When wearing it, Mario becomes Tanooki Mario. Like the Super Leaf power-up, after a running start it allows Mario to jump up and fly/glide in the air for a certain period of time. The Tanooki Suit differs in its unique ability to transform Mario into a statue for a few seconds, during which he is invincible but unable to move. In statue form, he can destroy some otherwise invincible enemies by landing on them.
If Mario uses a P-Wing while wearing the Tanooki Suit, he keeps the suit while gaining the permanent flight ability of the wing.
The Tanooki Suit is most certainly inspired from the Japanese tanuki, a racoon dog that has a mischevous behavior and shapeshifting powers in Japanese mythology.