Show Posts

121

**Stakeholder Proposals / @Delegates: Please upgrade to 0.8.* ASAP!!**

« on: March 24, 2015, 09:40:03 pm »

Delegate participation rate is down to 85% because some delegates haven't updated their client!

If they haven't updated when I wake up tomorrow I will remove them from my slate!

122

Stakeholder Proposals / [Disclaimer] Delegates run and maintained by "xeroc"

« on: March 24, 2015, 07:20:05 pm »

Hey friends,

in order to have information public: I just received the signing key for "del.fav" and will sign blocks for him and publish price feeds.

As a summary, I am in control of the signing keys for the following (maintained) delegates:

delegate.xeroc
del.fav

As some of you know, I am uncomfortable with running 6 or more delegates (https://bitsharestalk.org/index.php?topic=7673.new#new)
and I still consider this my upper bound!

Just wanted to let you guys know!

123

General Discussion / Quickly generate a paperwallet (PDF/SVG) using python tools

« on: March 19, 2015, 12:44:41 pm »

Installation of libraries:

Code: [Select]

git clone https://github.com/xeroc/bitshares-pytools
cd bitshares-pytools/python-bitsharestools  ## requires python2-ecdsa
python2 setup.py install --user

easy_install-2.7 qrcode --user     ## QRcode library
easy_install-2.7 lxml --user       ## SVG editing
easy_install-2.7 pypdf2 --user     ## PDF library
easy_install-2.7 svg2pdf --user    ## SVG2PDF library

Create a PDF paperwallet

Code: [Select]

cd bitshares-pytools/paperwallet
python2 genbulkwallets.py --number 4

Create a BIP38 encrypted PDF paperwallet

Code: [Select]

cd bitshares-pytools/paperwallet
python2 genbulkwallets.py --number 4 -encrypt

Result

Big thanks for cass to deliver a nicely looking initial paperwallet (spanish only atm - more to come)

124

General Discussion / [Experimental] Coldstorage with offline signing using Python2

« on: March 18, 2015, 08:59:18 pm »

Warning: This is untested and highly experimental software. Use at your own risk and only with minor amounts of funds!

Download & Installation:

Code: [Select]

git clone https://github.com/xeroc/bitshares-pytools
cd bitshares-pytools
cd python-bitsharesrpc
python2 setup.py install --user
cd ..
cd python-bitsharestools  ## requires python2-ecdsa
python2 setup.py install --user

optionally: python2-qrtools

Cold Storage Solution for BitShares

What is this?
This is a set of tools for cold storage and offline signing of balance
transactions, i.e., withdraw funds from a cold storage address and putting them
into a hot wallet (address).

Requirements

python-bitsharesrpc (for online part)
python-bitsharestools (for offline signin)
(optional) python2-qrtools (for QR-code support)

What parts are there and what are they doing?
Two parts:

`online`
Just get the balance of the cold storage address.
Help:
python2 main.py -h
Example:

Code: [Select]

    $ python2 main.py --address BTS4CNbXqeEym7JopKYvL16qVKUe9kRMMC8x                                                                                                               ─┘
    Connecting to BitShares RPC
    Available Funds
    5.000000 EUR
    0.000000 BTS
    Stored in file availablefunds.txt (for offline tools)

By default writes a txt file `availablefunds.txt` to the current directoy. This
file has to be moved to the offline computer for construction of the
transaction and signing process.

`offline`
Take the balance file from the `online` tool, ask for amount and assets to
transfer to the deposit address. The private key for signing is required in a
separated step and can be read by QR-code scanner. Note that only
one private key (i.e. one cold storage address) can be accessed at a time.
This script returns a readable (JSON formated) and signed transaction
instruction that can be pasted into the console of a connected BitShares
client. The signed transaction is also stored in a file `signedtx.txt` by
default.
Help:
python2 main.py -h
Example:

Code: [Select]

    $ python2 main.py --address BTSUTgrMqNAGqvhCJdYtuqVGkTCjP7ss3bh                                                                                                              ─┘
    Available funds:
    5.000000 EUR
    0.500000 BTS
    Give amount AND asset [10 BTS]: 5 EUR
    Going to withdraw:
    5.000000 EUR
    Want more? [Y/n] n
    Adding tx fee of 0.500000 BTS
    Please type private key [empty for QR scanner]: 5**************************************************
    This private key gives access to funds in address BTS*********************************
    --------------------------------------------------------------------------------
    + Raw and signed transaction for verification:
    --------------------------------------------------------------------------------
    {
	"operations": [
	    {
		"type": "withdraw_op_type", 
		"data": {
		    "claim_input_data": "", 
		    "amount": "50000", 
		    "balance_id": "BTSUTgrMqNAGqvhCJdYtuqVGkTCjP7ss3bh"
		}
	    }, 
	    {
		"type": "withdraw_op_type", 
		"data": {
		    "claim_input_data": "", 
		    "amount": "50000", 
		    "balance_id": "BTSG9SrG1qe2EtDbJkjbTUN4epSNG755P1y7"
		}
	    }, 
	    {
		"type": "deposit_op_type", 
		"data": {
		    "amount": "50000", 
		    "condition": {
			"asset_id": 21, 
			"slate_id": null, 
			"type": "withdraw_signature_type", 
			"data": {
			    "owner": "BTSUTgrMqNAGqvhCJdYtuqVGkTCjP7ss3bh", 
			    "memo": null
			}
		    }
		}
	    }
	], 
	"slate_id": 0, 
	"signatures": [
	    "202315d908cfd96eb43ba003d0efbaa02ca9584c79dca1474ed4bc1511bbedbed1ce29bfa0e98f8b78dcabd9c127c50bda18f7d26d5b9f70f0a03bc3f9096f122f"
	], 
	"expiration": "2015-03-19T08:23:15"
    }
    --------------------------------------------------------------------------------
    + stripped output of signed transaction (issue this command in the BTS console):
    --------------------------------------------------------------------------------
    blockchain_broadcast_transaction {'operations':[{'type':'withdraw_op_type','data':{'claim_input_data':'','amount':'50000','balance_id':'BTSUTgrMqNAGqvhCJdYtuqVGkTCjP7ss3bh'}},{'type':'withdraw_op_type','data':{'claim_input_data':'','amount':'50000','balance_id':'BTSG9SrG1qe2EtDbJkjbTUN4epSNG755P1y7'}},{'type':'deposit_op_type','data':{'amount':'50000','condition':{'asset_id':21,'slate_id':None,'type':'withdraw_signature_type','data':{'owner':'BTSUTgrMqNAGqvhCJdYtuqVGkTCjP7ss3bh','memo':None}}}}],'slate_id':0,'signatures':['202315d908cfd96eb43ba003d0efbaa02ca9584c79dca1474ed4bc1511bbedbed1ce29bfa0e98f8b78dcabd9c127c50bda18f7d26d5b9f70f0a03bc3f9096f122f'],'expiration':'2015-03-19T08:23:15'}
    --------------------------------------------------------------------------------
    + signed transaction stored in file signedtx.txt
    --------------------------------------------------------------------------------

What's the procedure?
Online
1. Go into the `online` part of the program and define the connection parameters to a running BitShares client in the `config.py` file
2. Get your cold storage address and either put it into the `config.py` file or append it to the command with "--address BTS...."
3. Run the `online` part of the program (it will list the funds stored in the cold storage address)

Offline
1. Copy the balance file from the online tool over to the offline tool directory (on an offline computer)
2. Execute the `offline` program and optionally give the file name as parameter (see `python2 main.py -h` for help)
3. Define the amount and asset you want to withdraw from the cold storage address
4. Paste the recipient address (or scan it with a webcam as QR-code)
5. Paste the private key (or scan it with a webcam as QR-code) -- The private key will be verified prior to signing.
6. The `offline` program constructs and signs a BitShares transaction
7. Carry the output (console command) to a connected BitShares client and paste the command in the console (the signed transaction is also stored in a txt file in the same directory)
8. Wait for 1 confirmation.
9. Done

What remains to be done

Read Encrypted paperwallet
Find someone that can verify the code is doing what it should
Add voting_key support
What else?

Input?

P.S. I'd love to see this forum support markdown .. would make pasting my README alot easier

125

General Discussion / All time hight ...

« on: March 18, 2015, 01:52:51 pm »

In the number of transactions:

http://bitsharesblocks.com/assets/market

126

General Discussion / API changes for 0.7 [xpost from github]

« on: March 12, 2015, 07:19:59 am »

https://github.com/BitShares/web_wallet/issues/637

Quote

Accounts, contacts, and approvals are now 3 completely different types of records in the wallet backend. Previously they were all considered "accounts".

Modified:

wallet_account_create - just doesnt accept extra private data on creation
wallet_transfer -- now accepts contacts, public keys, addresses as the recipient in addition to account names
some of the fields in any wallet_account_record were removed:
is_my_account
approved
is_favorite

Removed:

wallet_get_name
wallet_account_set_favorite
wallet_account_set_approval
wallet_add_contact_account
wallet_transfer_to_legacy_address
wallet_transfer_to_address
wallet_transfer_to_public_account
wallet_transfer_from
wallet_account_update_private_data
wallet_list_favorite_accounts
wallet_list_unregistered_accounts
wallet_list_my_accounts
wallet_get_account_public_address
wallet_remove_contact_account
wallet_check_vote_status

Added:

wallet_list_contacts
wallet_get_contact
wallet_add_contact
wallet_remove_contact
wallet_list_approvals
wallet_get_approval
wallet_approve
wallet_set_custom_data

Quote

Removed:

wallet_asset_create
wallet_asset_update
wallet_asset_issue
wallet_asset_issue_to_addresses
wallet_asset_authorize_key

Added:

wallet_mia_create
wallet_uia_create
wallet_uia_issue
wallet_uia_issue_to_addresses
wallet_uia_collect_fees
wallet_uia_update_description
wallet_uia_update_supply
wallet_uia_update_fees
wallet_uia_update_active_flags
wallet_uia_update_authority_permissions
wallet_uia_update_whitelist

127

General Discussion / [OpenForDiscussion] Voting for a hardfork proposal

« on: March 10, 2015, 08:02:02 pm »

Hey friends,

in this discussion and this discussion people from the community want to get altcoins traded in BitShares DEX (as market pegged assets) ..

The questions would be how to get them into the DEX. Either someone* has to pay 500k BTS for the registration or the shareholders come to a consensus and let the next hardfork create those assets for free.

* altcoin community, individual or delegates

The issue I'd like to discuss (again) what criteria have to be met such that the developers can see a consensus of the shareeholders about which markets to open.

Obviously, a forum poll is work nothing. Hence, I'd like to propose (similar to toast's proxy delegate) to vote for 0%-delegates.
As I don't think they will make it into the TOP101 we should discuss what threshold those delegates have to pass in BTS votes in order to be interpreted as "consensus" among a set of shareholders .. obviously, a 51% stake vote will note work. maybe a 51% of the actively voting stake .. or maybe 51% of the votes counted for TOP1 delegates ..

Let's discuss

BTW. for those not understanding the reason for this: Take a look at coin voting @cryptsy @mintpal (prior to shutdown) and possibly others .. In short, marketing this idea to individual altcoin communities will separated those communities that want their token traded in the BTS DEX from those that don't care .. AND drive the BTS price, because votes only count as BTS (with the HUGE advantage that voting with your BTS stake does not make you loos your stake

)

Please discuss!

@toast @bytemaster @vikram @allotherdevs: what's your opinion?

128

General Discussion / Threshold signatures for Bitcoin wallets are finally here

« on: March 08, 2015, 04:46:04 pm »

https://freedom-to-tinker.com/blog/stevenag/threshold-signatures-for-bitcoin-wallets-are-finally-here/

stealth multisig sig ..

Shouldn't that also be possible in bitshares?

@bytemaster @toast @vikram @modprobe @pc

129

General Discussion / [Paperwallet] Python / SVG / automated

« on: March 04, 2015, 06:54:47 pm »

Hey friends,

I coded a new python tool to generate nicely scalable (SVG) paperwallets for BTS.
The following python libaries are required:
* csv
* qrcode
* lxml

Features
The following images and text boxes are individually replaced:

* QR code for address
* QR code for private key
* Address as text
* Amount
* Asset logo

Example
The file wallet-example.cvs contains an example for the input data required for this tool. The columns in this order are
* Private key in WIF format
* BTS address
* Amount
* Asset

Source:
https://github.com/xeroc/bitshares-pytools/tree/master/paperwallet

Example:

Have fun!

130

Stakeholder Proposals / Some price feeds are off several percent

« on: March 03, 2015, 05:03:31 pm »

@delegate.bitder @liondani @calabiyau @wackou

Would you please take a closer look at your delegate feed script. Your numbers
seem a little off:

Quote

Large deviation Feeds
+-----------------------------------------+-----+----------+--------------------------------------+
| delegate | top | numFeeds | asset |
+-----------------------------------------+-----+----------+--------------------------------------+
| jcalfee1-developer-team.helper.liondani | 19 | 15 | KRW, 11.70172244 (med +7.085%) |
| | | | BTC, 0.00003873 (med +4.817%) |
| | | | SILVER, 0.00064802 (med +7.092%) |
| | | | GOLD, 0.00000881 (med +6.838%) |
| | | | HKD, 0.08263500 (med +7.324%) |
| | | | RUB, 0.66621800 (med +8.059%) |
| | | | CNY, 0.06662300 (med +6.960%) |
| | | | CAD, 0.01334600 (med +7.930%) |
| | | | CHF, 0.01024015 (med +7.531%) |
| | | | AUD, 0.01368000 (med +7.889%) |
| | | | GBP, 0.00693200 (med +7.285%) |
| | | | JPY, 1.28000000 (med +7.811%) |
| | | | EUR, 0.00952200 (med +7.317%) |
| | | | USD, 0.01065600 (med +7.347%) |
| | | | |
| delegate.liondani | 43 | 15 | KRW, 11.70172244 (med +7.085%) |
| | | | BTC, 0.00003873 (med +4.817%) |
| | | | SILVER, 0.00064802 (med +7.092%) |
| | | | GOLD, 0.00000881 (med +6.838%) |
| | | | HKD, 0.08263500 (med +7.324%) |
| | | | RUB, 0.66621800 (med +8.059%) |
| | | | CNY, 0.06662300 (med +6.960%) |
| | | | CAD, 0.01334600 (med +7.930%) |
| | | | CHF, 0.01024015 (med +7.531%) |
| | | | AUD, 0.01368000 (med +7.889%) |
| | | | GBP, 0.00693200 (med +7.285%) |
| | | | JPY, 1.28000000 (med +7.811%) |
| | | | EUR, 0.00952200 (med +7.317%) |
| | | | USD, 0.01065600 (med +7.347%) |
| | | | |
| calabiyau | 73 | 19 | SILVER, 0.00061426 (med .513%) |
| | | | SGD, 0.01373629 (med .544%) |
| | | | HKD, 0.07816006 (med .512%) |
| | | | RUB, 0.62655999 (med .627%) |
| | | | SEK, 0.08343260 (med .591%) |
| | | | NZD, 0.01333725 (med .564%) |
| | | | MXN, 0.15119664 (med .686%) |
| | | | CAD, 0.01255637 (med .545%) |
| | | | CHF, 0.00967162 (med .561%) |
| | | | AUD, 0.01287488 (med .539%) |
| | | | JPY, 1.20615399 (med .591%) |
| | | | EUR, 0.00900955 (med .542%) |
| | | | USD, 0.01007818 (med .526%) |
| | | | |
| wackou-delegate | 91 | 19 | KRW, 11.13231506 (med .874%) |
| | | | |
| delegate.bitder | 99 | 19 | KRW, 11.34300000 (med +3.802%) |
| | | | BTC, 0.00003880 (med +5.020%) |
| | | | SILVER, 0.00062785 (med +3.757%) |
| | | | GOLD, 0.00000854 (med +3.540%) |
| | | | TRY, 0.02606900 (med +3.563%) |
| | | | SGD, 0.01402950 (med +3.711%) |
| | | | HKD, 0.07989850 (med +3.770%) |
| | | | RUB, 0.64277000 (med +4.256%) |
| | | | SEK, 0.08576900 (med +4.436%) |
| | | | NZD, 0.01373100 (med +4.562%) |
| | | | CNY, 0.06467500 (med +3.833%) |
| | | | MXN, 0.15522000 (med +4.392%) |
| | | | CAD, 0.01293500 (med +4.607%) |
| | | | CHF, 0.00991020 (med +4.066%) |
| | | | AUD, 0.01323350 (med +4.367%) |
| | | | GBP, 0.00670630 (med +3.792%) |
| | | | JPY, 1.23380000 (med +3.920%) |
| | | | EUR, 0.00923360 (med +4.067%) |
| | | | USD, 0.01034800 (med +4.245%) |
| | | | |
+-----------------------------------------+-----+----------+--------------------------------------+

131

General Discussion / List your Feature Requests for a coldstorage solution written in python

« on: March 01, 2015, 05:15:46 pm »

Hey friends,

I started digging into offline signing and have working python code to do the ecdsa signing. It came to me that the code can be easily modified to implememt offline coldstorage signing.

Before starting to implement this I would like to ask the community for input .. like feature request of any kind ...

But note that i can work on this only in my spare time .. so it might take some time .. but the most difficult part (the signing) is already done and working.

I would also love to see someone proof read the implementations before it is used for bigger amounts of funds ..

Regards
- Fabi

132

General Discussion / 100+ new users/day for the last two days

« on: February 20, 2015, 04:45:24 pm »

Looks promising:

133

Stakeholder Proposals / [Howto] Put your delegate's owner key on ice while keeping signing blocks

« on: February 18, 2015, 08:42:50 am »

Hey friends,

yet another quick howto related to the howto about securing owner keys.
This time: Secure your owner key and keep signing blocks for delegates

TL;DR;:
- secure the owner key of your delegate
- continue signing blocks
- keep your votes in even if your VPS with the signing key is compromised

This is not a cold storage solution, but rather a howto for having just the one necessary key on the delegate machine which is NOT the owner key of the registered account name (to which votes/approvals are bound!)

I recommend EVERY delegate to consider this howto!

Important Remark:
This tutorial will add a RANDOM key as a new delegate signing key. Hence this signing key cannot be regenerated or derived from the delegate's owner key.
The random key will be added to your wallet (into your delegates' account) and continue signing as usual.
It is REQUIRED that you let the delegate run for at least ONE round (better 2 or more .. say 60 minutes or so) with BOTH keys in the wallet.
The reason for this is the SECRET that has to be revealed using the 'old' signing key while signing the block with the new signing key.

Howto:

1) make a backup of your wallet

Code: [Select]

wallet_backup_create
(Optional) Extract your owner key for cold storage or what ever:

Code: [Select]

wallet_dump_account_private_key <delegatename> owner_key

2) Generate a new private key
Several tools exist to do so:
- one is located near the bitshares executable (if you compiled yourself) in
"programs/utils/" and is called bts_create_key
- In the bitshares-pytools repository (github.com/xeroc/) there is a tool called
genbtskey.py (in tools) that generates a new privkeypubkey
- you can also use bitshares-js as shown
here

As a result we will get something like this

Code: [Select]

  "public_key"      : "BTS8RCDZ8aPRxJYVnK7KWmqnTjTPj4H8oY1KtzBcFqbzSp14AGpzh", <<--- pubkey
  "wif_private_key" : "5Hwb7G481UsKnjPEb135iWHRGDvLWH5nW6QH4b5vcKS7gGFkdGx",   <<-- privkey
  "native_address"  : "BTSe3YhhRrTfgkGmEECw7yxZvpaQkSToEgS", (not required here)

3) import the private key into your account:

Code: [Select]

wallet_import_private_key <wif-from-2)> <delegatename> false false
## example:
wallet_import_private_key 5Hwb7G481UsKnjPEb135iWHRGDvLWH5nW6QH4b5vcKS7gGFkdGx delegate.xeroc false false

4) Fund the delegate with 0.5 BTS to pay for the update transaction

5) Update the signing key

Code: [Select]

wallet_delegate_update_signing_key <delegatename> <delegatename> <pubkey-from-2)>
## example:
wallet_delegate_update_signing_key delegate.xeroc delegate.xeroc BTS8RCDZ8aPRxJYVnK7KWmqnTjTPj4H8oY1KtzBcFqbzSp14AGpzh

Done.

Notes:
- the key from step 2) is now required by any machine of yours that has the
delegate running in eventually has to sign a block
- your delegate should continue signing blocks as usual as we imported the
required key in step 3)
- you can dump the signin key from that account again at any time by issuing:

Code: [Select]

wallet_dump_account_private_key <delegatename> active_key

If you want to setup a new wallet that contains only the signing key, the only
thing you have to do is import the privkey with

Code: [Select]

wallet_import_private_key 5Hwb7G481UsKnjPEb135iWHRGDvLWH5nW6QH4b5vcKS7gGFkdGx

The client can figure out the delegates name automatically.

Make sure to between step 5) and moving over to a new wallet with the new key,
it has passed at least one round if delegates. I recommend to run the steps 1)
to 5) 24h before creating a new signing-key-only wallet.

The brave users can take a look at this script:
* https://github.com/xeroc/bitshares-pytools/blob/master/delegate-changetosigningkeysonly/main.py
which is doing exactly the steps 1)-5)

134

General Discussion / [Howto] Securing your Owner key while using your funds

« on: February 17, 2015, 09:33:21 pm »

Hey friends,

TL;DR;:
- secure the owner key of your registered account
- continue using your account by means of the active_key

this quick tutorial is meant for people that want to put their account name's private key on ice.
This is not a cold storage solution for your funds but for the account
which is registered on the blockchain.
Note that open market orders are not recoverable from the new keys. So
please close your open orders before doing this.

Background:
The blockchain differenciates between at least two pub/priv keys:

owner_key
- 'owns' the account on the blockchain.
- it's like the master of everything.
- all keys are derived from this. Comparable with the seed of HD wallets from Bitcoin.
- can NOT be updated/changed on the blockchain

active_key
- derived from owner_key
- used for (TITAN and non-TITAN) transaction to a registered account name
- used to derive market keys .. (at least that's my understanding)
- can be updated/changed on the blockchain

signing_key (delegates only)
- used to sign blocks (different chapter, different howto)

Howto secure your account's owner key:
1) Make a backup of your wallet

Code: [Select]

wallet_backup_create

2) set a new active key

Code: [Select]

wallet_account_update_active_key <accountname> <payingAccountName>

with <accountname> denoting the account name for which you want to
update to a new active key and [t]<payingAccountName>[/tt] is the account which
is funded and pays the transaction fee. The client itself derives a new
active_key (deterministically from the owner key) and sends an update
transaction to the network. You current wallet will still be able to receive
new funds.

3) wait for one or two blocks

4) Dump the new active key

Code: [Select]

wallet_dump_account_private_key <accountname> active_key

5) create new wallet

6) import private key from above into new wallet

Code: [Select]

wallet_import_private_key <wif> "" false false

The "" tells the client to figure out the account name automatically and
"false false" tells the client to not 'create' but import an existing account
and not rescan the blockchain (which we will do manually because we have some
more accounts to secure

)

7) Repeat 2) to 6)

8 ) Rescan

Code: [Select]

rescan

Done. Your funds should all appear again. Even those that have been traded on the blockchain.

For the brave guys in the community: I wrote a python script to do the above
steps for all accounts (it worked here

)
https://github.com/xeroc/bitshares-pytools/blob/master/user-tonewactivekey/main.py
Sample output:

Code: [Select]

# Reading accounts                                                                                                                                                                                                 
                                                                                                                                                                                                                   
                                                                                                                                                                                                                   
## setting new active keys                                                                                                                                                                                         
-     a.delegate.xeroc
-     b.delegate.xeroc
-     c.delegate.xeroc
-     d.delegate.xeroc
-       delegate.xeroc
-     e.delegate.xeroc
Error changing active key for exchange.xeroc. Probably not able to pay. Please fund account.
-       exchange.xeroc
Error changing active key for exchange.xeroc. Probably not able to pay. Please fund account.
-     f.delegate.xeroc
-        payouts.xeroc
-     xeroc-delegate-1
-     xeroc-delegate-2
-     xeroc-delegate-3
-     xeroc-delegate-4
-     xeroc-delegate-5
-     xeroc-delegate-6
-     xeroc-delegate-7
-     xeroc-delegate-8
-     xeroc-delegate-9


## waiting two blocks to confirm


## moving funds to new active keys
--       exchange.xeroc : sending XXXXXXXX BTC
--       exchange.xeroc : sending XXXXXXXX EUR
--        payouts.xeroc : sending XXXXXXXX EUR
--        payouts.xeroc : sending XXXXXXXX USD
--     xeroc-delegate-1 : sending XXXXXXXX EUR
--     xeroc-delegate-1 : sending XXXXXXXX USD


## waiting two blocks to confirm

## new active keys
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wallet_import_private_key 5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

DISCLAIMER:

THE TUTORIAL IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

135

Stakeholder Proposals / xeroc's price feed broken

« on: February 09, 2015, 03:43:59 pm »

I just realized that my current implementation for the price feeds is broken unless you have funds in the delegates account:
The wallet used to have a 'payee' option for wallet_publish_fees, which is no more with 0.6.0 .. very unfortunate!

I recommend everyone using my script to fund your delegates with some BTS .. the drawback with this is that due to disabled TITAN scanning, your delegate will not be able to see your funds unless you enable scanning and rescan the blockchain .. sucks

paging @vikram : what's the reason for this change?

Profile Info

Topics - xeroc

**Stakeholder Proposals / @Delegates: Please upgrade to 0.8.* ASAP!!**

Stakeholder Proposals / [Disclaimer] Delegates run and maintained by "xeroc"

General Discussion / Quickly generate a paperwallet (PDF/SVG) using python tools

General Discussion / [Experimental] Coldstorage with offline signing using Python2

General Discussion / All time hight ...

General Discussion / API changes for 0.7 [xpost from github]

General Discussion / [OpenForDiscussion] Voting for a hardfork proposal

General Discussion / Threshold signatures for Bitcoin wallets are finally here

General Discussion / [Paperwallet] Python / SVG / automated

Stakeholder Proposals / Some price feeds are off several percent

General Discussion / List your Feature Requests for a coldstorage solution written in python

General Discussion / 100+ new users/day for the last two days

Stakeholder Proposals / [Howto] Put your delegate's owner key on ice while keeping signing blocks

General Discussion / [Howto] Securing your Owner key while using your funds

Stakeholder Proposals / xeroc's price feed broken