How to generate your very own Bitcoin private key

It's finally here! Tautulli v2 [beta] (formerly PlexPy v2)

It's finally here! Tautulli v2 [beta] (formerly PlexPy v2).

The long awaited for PlexPy v2 is finally here with a new name Tautulli! Also check us out on the new Plex Labs!
I'm looking for some brave people to help me test some new feature before I fully release them. It's a very big update so I want to make sure everything is working.
Warning: This may mess up your PlexPy install and/or your database. You have been warned. Only join the beta if you are serious about testing and reporting bugs, otherwise I strongly recommend you wait until the final release.


v2.0.0-beta (2017-12-18)

v2.0.1-beta (2017-12-19)

v2.0.2-beta (2017-12-24)

v2.0.3-beta (2017-12-25)

v2.0.4-beta (2017-12-29)

v2.0.5-beta (2017-12-31)

v2.0.6-beta (2017-12-31)

v2.0.7-beta (2018-01-01)

v2.0.8-beta (2018-01-03)

v2.0.9-beta (2018-01-03)

v2.0.10-beta (2018-01-04)

v2.0.11-beta (2018-01-05)

v2.0.12-beta (2018-01-07)

v2.0.13-beta (2018-01-13)

v2.0.14-beta (2018-01-20)

v2.0.15-beta (2018-01-27)

v2.0.16-beta (2018-01-30)

v2.0.17-beta (2018-02-03)

v2.0.18-beta (2018-02-12)

v2.0.19-beta (2018-02-16)

v2.0.20-beta (2018-02-24)

v2.0.21-beta (2018-03-04)

v2.0.22-beta (2018-03-09)

"I'm interested! Where do I sign up?"

Assuming you already have PlexPy installed using git, all you need to do is follow these steps:
  1. Backup your database! Go to the PlexPy Settings > General tab > Backup Database. You will need to restore this if something messes up. I'm not helping you if you mess up your database and you didn't create a backup.
  2. Shut down PlexPy by going to Settings > Shutdown.
  3. Using your shell/command line, run the following from the PlexPy folder:
    git fetch git checkout beta 
  4. Start Tautulli as normal.
  5. Post below if you find any bugs (include logs). Please don't post on GitHub issues or the Plex forum thread with bugs/issues from the beta test. If you do, I will laugh at you and delete your post.
    • Please read the issues guidelines before report any problems, and refer to the FAQ for common issues.
    • New features can be submitted on FeatHub (use the search to see if it has already been requested). Please read the feature request guidelines before requesting new features.
    • Join the Discord Server chat for faster help and general chit chat. (Note: the Gitter chat is no longer being used.)
If you want to revert back to the version of PlexPy before beta testing:
Warning: You will not be able to use your v2 database with v1!
  1. Shut down Tautulli by going to Settings > Shutdown.
  2. Restore your backed up plexpy.db file (it can be found in the backup folder).
  3. Using your shell/command line, run the following from the PlexPy folder:
    git checkout master 
  4. Start PlexPy as normal.
Buy me a coffee if you want to support the project! - PayPal | Bitcoin: 3FdfJAyNWU15Sf11U9FTgPHuP1hPz32eEN

Answers to your questions:

  • Why did you call it Tautulli?
    • Because it sounds cool and means "to watch or monitor" in Inuktitut.
  • I don't like the new name!
    • That's too bad. Also, that is not a question.
  • When will v2 be out of beta?
    • When I feel like there are no more major bugs with it. SoonTM.
  • Is there an iOS app?
    • No, there isn't. It costs money to be an iOS developer.
submitted by SwiftPanda16 to PleX [link] [comments]

Monero Payment Bot POC

So a company I work for held an annual Hackathon yesterday. The company's main job is to provide customer-facing software solutions to utility companies. Things like payments, outage reporting, notifications, etc...
My team ran with the idea of an NLP bot solution that would allow users to pay their outstanding utility account balance using cryptocurrency. Of course, being a long-time Monero hodler I couldn't pass up this chance to provide Monero with some visibility.
We won first place in the office I work out of, and we presented to the entire company today. We lost to a team in another location by one vote unfortunately, but at least I was able to get the Monero logo burned into the eyeballs of every employee at this company. :D
Here's a screenshot of our bot conversing through a Slack integration. Not bad for only 8 hours of work!
A few notes for any developers out there who are interested in how we accomplished this.
The idea is that this will be used a jumping off point to allow cryptocurrency payments through our product in the future. This makes sure that Monero is in that plan. If anyone is feeling generous and wants to give our team a pat on the back in the form of a tip, we'd appreciate it! Here's our Monero address: 44STxxzXoPBLb7vc8cZTjGFW85eEeRcqwehkAbQAYKnuR6xRxB2Kycy3vv3iSioM3fbdLJkAWTqfvJYm9cd6sST9NoZWXF2
EDIT: A big thank you to whoever tipped!
submitted by AbstractStateMachine to Monero [link] [comments]

Real World Model for a Bitcoin Blockchain Election

Real World Model for a Bitcoin Blockchain Election
tl;dr The Bitcoin Blockchain can be used to ensure every vote in a government election is counted and no mass vote manipulation has occurred. This can replace papeelectronic vote counting as used today.
Bitcoin enables you to publicly track transactions on it’s blockchain. These transactions can also have arbitrary meaning. For example, a vote one way or another.
You could vote for Option A or Option B by sending a tiny dust amount to Address A or to Address B. These options could each represent candidates seeking government election.
Imagine that the address with the greatest number of incoming transactions during the specified time wins the vote, regardless of ending balance.
Voters can periodically check their vote transaction to make sure it still exists and is confirmed. Each voter can see the total vote counts and perform blockchain analysis of the election as desired. This means we can reasonably assume every vote is counted, and no votes can be redirected to another candidate.
Problem 1: How do you ensure voters don’t vote twice? Bitcoin addresses can be generated at will.
Bitcoin addresses can be generated in mass and pre-qualified ahead of the election. Only pre-qualified addresses can have their vote transaction counted.
A Bitcoin address is pre-qualified by having a government published “master election address” confirm a transaction to it before the election starts. The address is now provably linked to the election and now has a balance that can be re-allocated during the election.
All voters can see the “master election address” and every Bitcoin address it’s pre-qualified. Votes from addresses that not pre-qualified are not counted. Only the last vote from a pre-qualified address is counted.
Now we can ensure that only a limited number of votes can occur.
Problem 2: Distributing control of the pre-qualified addresses to voters.
We already have a system of distributing ballots to voters - polling stations – let’s use them.
The pre-qualified address keypairs are printed to paper wallet ballots. The paper wallet ballots are distributed to the polling stations and have no personally identifiable information on them. They may have some basic security features to them – such as folded and then connected perforated edges that need to be broken (like a paystub).
The paper wallet ballots replace traditional ballots for all voters.
Each polling station receives an extra % of ballots - for sampling, new voter registrations etc. This surplus amount must be enough to cover logistics issues of voters, but not enough to allow “ghost votes”.
An online spreadsheet is released by the government ahead of the vote, documenting each address that has been pre-qualified and it’s associated polling station. This allows everyone to see how the addresses have been allocated, and to ensure that the right numbers are delivered to each polling station. This can also be cross-referenced with the Bitcoin blockchain. On election day, polling station staff can randomly draw ballots and ensure they have been allocated properly on the spreadsheet.
This spreadsheet can also list published destination (candidate) addresses for each polling station and other pertinent information. Each candidate has a pre-authorized address made public for the sole purpose of the election. Those addresses will be monitored during the election time to determine the outcome. Any transactions sent before or after is disregarded.
It is assumed that pre-qualified addresses will be loaded with enough coin to pay dust and a reasonable transaction fee. The voting transaction does not need to confirm in the next block. Today, 1 cent would be enough. Destination addresses could be controlled by the government or provided ahead of time by a candidate.
We now have three groups of addresses, all created specifically for one election:
1) The one "Master Election Address"
2) Millions of pre-qualified Bitcoin addresses as ballots
3) Destination addresses for each candidate running for election
Election Day
Voters appear at their polling stations, identify with ID and are given a ballot. The ballot contains a public and private key, and associated QR codes. It's really just a paper wallet with a preloaded cent, from the "Master Election Address".
They can use a “voting machine” to scan the QR code of their private key and easily choose from a list of options to vote for. Once they confirm their vote, a transaction is broadcast from their pre-qualified address to the candidate's address. A receipt is printed with TX info, that they can lookup at home.
This means that any issues with voting machines will be immediately identifiable, as it’s reasonable to assume some percentage of people will actually verify their transaction. Electronic voting machines have a reputation for re-directing votes or not counting them at all.
Alternatively, voters could use a government created mobile App to scan their paper wallet ballot, cast their vote easily with the public pre-programmed destination addresses for that election, and store a copy of their TX details. This can be done outside of the polling location, reducing the load on the location’s resources.
Finally, voters can use their own trusted Bitcoin wallet and some expertise to import the private key (not sweep!) and place their vote using the publicly available data.
Only votes cast within the election time are counted. Votes from non-pre-qualified addresses are not counted. Only the last transaction from a pre-qualified address is counted.
Polling station staff watch the un-used ballots until the election time is over, at which point they are only worth the dust on them and sent back to main office. Transactions sent after the election time are not counted.
Anyone can now see the results and check to see if their vote was manipulated. They can also track voter turnout and suspicious polling station activity (all ballots used etc). As long as a blockchain with enough power like Bitcoin is used, votes can be considered secure.
The election time may need to be longer than 12 hours if 300 million Americans attempted to vote in 12 hours (not enough space in blocks for all votes).
Voters can see how other voters are voting in real time. Some voters may then hold out until later in the election time when partial results are available, compounding the effect.
Deal breaker? Still seems better than what we do now. Any thoughts on pre-qualified addresses, ballot distribution, vote tracking etc?
EDIT: Typos etc.
submitted by jamierobinsondotco to Bitcoin [link] [comments]

sx Bitcoin utilities (new installation instructions and information inside)

My aim with this project is to provide a set of modular Bitcoin commandline utilities, that admin types can engage with Bitcoin functionality without having to write code.
By chaining all these commands together in different ways, you can do offline transactions, maintain a wallet, work with deterministic keys, ...
It would be cool to see Bitcoin wallets written in bash script using these tools to handle the core functionality. I believe the more we give good tools to the community, the more we can decentralise development and increase access to the core technology for all types.
Use this bash shell script to install sx:


$ wget $ sudo bash ./ 
sx should now be installed.
Installation commencing NOW. ... 


Development repository:
My Bitcoin address (from
I want your feedback and suggestions! [email protected]
Type sx-TAB to see a list of all the sx commands.
Command Description
sx-addr see Bitcoin address of a private key.
sx-broadcast-tx broadcast tx to network.
sx-mktx create an unsigned tx.
sx-newkey create a new private key.
sx-newseed create a new deterministic wallet seed.
sx-mpk extract a master public key from a deterministic wallet seed.
sx-genpriv generate a private key deterministically from a seed.
sx-genpub generate a Bitcoin address deterministically from a master public key.
sx-mnemonic work with Electrum compatible mnemonics (12 words wallet seed).
sx-sendtx send tx to a single node.
sx-showtx show the details of a tx.
sx-sign-input sign a tx input.
sx-genqr generate Bitcoin QR codes offline.
sx-balance show balance of an address.
sx-history get list of output points, values, and their spends for an address. grep can filter for just unspent outputs which can be fed into mktx.
sx-watchtx watch transactions from the network searching for a certain hash.

Simple Bitcoin Client

Try this to make a mini-wallet.
$ cd src/ $ sx-newkey 5KPFsatiYrJcvCSRrDbtx61822vZjeGGGx3wu38pQDHRF8eVJ8H $ sx-newkey > private.key $ cat private.key | sx-addr 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz 
Now send some funds to your address (0.01 BTC).
In this example we will send the funds to 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe.
100000 Satoshis (0.001 BTC) in total. 90000 Satoshis (0.0009 BTC) to send. 10000 Satoshis (0.0001 BTC) for the fee. 
Use (or the history tool provided here) to lookup the output for this address. Note down the transaction hash and transaction index.
Here is a screenshot of
We can see the tx hash is: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3 And there is a single output at index 1 that we want to spend (the 2nd one for 0.001 BTC).
Construct the transaction:
$ sx-mktx txfile.tx -i 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:1 -o 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe:90000 
Because there is 100000 Satoshis going in, but only 90000 Satoshis out, the remaining 10000 Satoshis (0.0001 BTC) will be taken by the Bitcoin network as a fee. This is how fees work internally in Bitcoin.
'showtx' allows inspecting of tx files.
$ sx-showtx txfile.tx hash: 4d25b18ed094ad68f75f21692d8540f45ceb90b240a521b8f191e95d8b6b8bb0 version: 1 locktime: 0 Input: previous output: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:0 script: sequence: 4294967295 Output: value: 90000 script: dup hash160 [ 18c0bd8d1818f1bf99cb1df2269c645318ef7b73 ] equalverify checksig address: 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe 
Note that the input script is empty.
We will now sign the first input using our private key.
$ cat private.key | sx-sign-input txfile.tx 0 $ sx-showtx txfile.tx hash: 4a8be467fb75f0f757649348dbb05762142236ec236ac9e55e4683d7083ffca2 version: 1 locktime: 0 Input: previous output: 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:0 script: [ 304602210083f8b5131f6399cdc01ed8368f6137f288f771e40834a94d65cee6b380fec873022100da5ed6d1d283f228752a88c2d6f629587b2a6fbc102202ae7c20f48af7c0533c01 ] [ 04e3af7cdfaab6ba2f14001a7ea0a490f40c6ba43607be92a05111d2e8fc1eecf6fa2c248b3e25ddf7db081684f6f49dc83fd7b9b5a3a88a2e6b83b918f8972351 ] sequence: 4294967295 address: 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz Output: value: 90000 script: dup hash160 [ 18c0bd8d1818f1bf99cb1df2269c645318ef7b73 ] equalverify checksig address: 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe 
Now the input script is prepared, and the tx is signed.
Broadcast the final tx to the Bitcoin network.
$ sx-broadcast-tx txfile.tx 
Or to send it to one Bitcoin node (like a localhost one), then use:
$ sx-sendtx txfile.tx localhost 4009 

QR Code Generator

$ sudo apt-get install qrencode $ sx-genqr 13Ft7SkreJY9D823NPm4t6D1cBqLYTJtAe qrcode.png 

Deterministic Wallet

$ sx-newseed > wallet.seed $ cat wallet.seed b220b5bd2909df1d74b71c9e664233bf $ cat wallet.seed | sx-mpk > master_public.key 
Now you can generate your private keys for whatever number:
$ cat wallet.seed | sx-genpriv 0 5Jmb4EYzEqj63rkPwADFY7WyGV2kga3YB1HfDAzg9dHNG57NMPu $ cat wallet.seed | sx-genpriv 1 5KjCYpPyxU2e88S57b1naKUsJ1JNjCudkFSQPxqcYyBYgzzahNe 
You can use either the master_public.key or the wallet.seed for generating Bitcoin receive addresses. But you cannot use the master_public.key for generating the private keys for spending those Bitcoins.
$ cat master_public.key | sx-genpub 0 1a4b47AC4ydSnAAcTNH1qozHq2pwJb644 $ cat wallet.seed | sx-genpub 0 1a4b47AC4ydSnAAcTNH1qozHq2pwJb644 
For Electrum compatible 12 word seeds, use the mnemonic tool.
$ echo 148f0a1d77e20dbaee3ff920ca40240d | sx-mnemonic people blonde admit dart couple different truth common alas stumble time cookie $ echo "people blonde admit dart couple different truth common alas stumble time cookie" | sx-mnemonic 148f0a1d77e20dbaee3ff920ca40240d 

balance/history (Advanced)

The balance/history tools can then use a network connection to make requests against the load balancer.
$ echo 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz | sx-balance 100000 $ echo 134HfD2fdeBTohfx8YANxEpsYXsv5UoWyz | sx-history Output Hash:Index Output Height Value (Satoshis) Spend Hash:Index Spend Height 97e06e49dfdd26c5a904670971ccf4c7fe7d9da53cb379bf9b442fc9427080b3:1 247683 100000 Unspent 230529504 
It's possible to run as many backend workers as you like. The load balancer (obbalancer) will distribute requests evenly among the backends. Use to view debug info from the worker. Each worker must have their own unique copy of the blockchain database.
See the Obelisk config files in /uslocal/etc/obelisk/. The sx config file is stored at ~/.sx.cfg (there's an example at /uslocal/share/sx.cfg). You can change this configuration parameter using './configure --sysconfigdir=/etc/'. By configuring different workers and load balancers, you can run multiple setups on the same host. By default it is no pointing at my development server, but I will change this soon and migrate to a new host. Also I make no guarantees about stability or compatibility.
submitted by genjix to Bitcoin [link] [comments]

Bitcoin QR Code Scams Found on Google Search Pages How To Access The Users Webcam To Scan Bitcoin QR Codes Tutorial hack code block chain bitcoin private key 30/10/2017 Hack bitcoin (private script) 2019 QR Bitcoin Code Generator

Visual bitcoin private key generator. The square 16x16 is used for generation purposes, where each cell is one bit - 0 or 1. Make your visual drawings or use the generator in coin mode just fllipping the coin and fill the corresponding cell depending on the coin outcome. Wallet Address QR Code 🔑 SHOW PRIVATE KEY. ASN.1 Key. Public Key. HASH160. Generate Armory & Electrum Chains. Generation Method. Armory Electrum . Root Key. Secure Random . Chain Code. Paper Backup. Primary Addresses. Change Addresses. Wallet Format. CSV JSON. Chain. Bitcoin Transaction Builder. Use this tool to create a new BTC transaction (tx) Build Transaction From. Private Key JSON ... Free Online QR Code Generator to make your own QR Codes. Supports Dynamic Codes, Tracking, Analytics, Free text, vCards and more. QR Code Scanning. After clicking the "validate" tab, you can click the QR code icon to launch the camera QR code scanner. Any valid QR code will scan, but for the verify feature to work this needs to be a private key for your paper wallet. This is a great way to test whether or not you can successfully decode your BIP38-encrypted private key prior to loading your wallet with funds. The Bitcoin Address where you will send your fee will be shown on the screen with a QR Code below. For each transaction there will be generated a new Bitcoin Address. After this step, you will receive your free Bitcoin on your personal Bitcoin Wallet through Blockchain. How to create a Bitcoin Wallet Address At the moment the most popular wallet is the one from Blockchain or Electrum. It is ...

[index] [20562] [6972] [40183] [29950] [27548] [35876] [12733] [74] [19297] [18720]

Bitcoin QR Code Scams Found on Google Search Pages This video is unavailable. Watch Queue Queue Bitcoin QR Code Scams Found on Google Search Pages - Duration: 3 ... How to Generate a Private Key from a Bitcoin watch only address - Duration: 11:01. Bitcoin Daytrader Recommended for you. 11:01 ... Ferramenta que transforma seu endereço BTC em QR Code Researchers have discovered that the majority of links returned in Google search pages for Bitcoin QR code generators are for fake or scammy websites. ... How to accept Bitcoin. No computers. Don't have to be an IT whiz. Just print out a piece of goshdarned paper. We used wallet in this v...