Quote from: akashic on June 20, 2018, 10:56:10 AM
1 - I started work on a Discord tip bot days ago and should've mentioned that when I outlined the issues I was having - https://gitlab.com/metaperl/btsbot

My bot can go by the wayside or he can do whatever he wants with my code that abides by the LGPL. This would free me to move on to other projects.

1 - I started work on a Discord tip bot days ago and should've mentioned that when I outlined the issues I was having - https://gitlab.com/metaperl/btsbot

2 - I ran into some roadblocks with the pybitshares module.
* I filed a ticket ( https://github.com/bitshares/python-bitshares/issues/110 ) and have received no response.
* There has been no response to my questions here - https://bitsharestalk.org/index.php?topic=26713.msg319438#msg319438
* There has been no response to my questions here, either - https://bitsharestalk.org/index.php?topic=26712.msg319437#msg319437
* I messaged "xeroc" (Fabian Schuh) directly on Telegram with my issues he did not reply to me.

In looking at the following code:

from pprint import pprint
from bitshares import BitShares

testnet = BitShares(
    "wss://node.testnet.bitshares.eu",
    nobroadcast=True,
    bundle=True,
)

testnet.wallet.unlock("supersecret")

testnet.transfer("init0", 1, "TEST", account="xeroc")
testnet.transfer("init1", 1, "TEST", account="xeroc")
testnet.transfer("init2", 1, "TEST", account="xeroc")
testnet.transfer("init3", 1, "TEST", account="xeroc")

pprint(testnet.broadcast())

We see that assets are transferred from the account xeroc to init0, init1, init2, and init3.

My questions are:

• was the wallet created using code similar to this: http://docs.pybitshares.com/en/latest/index.html#create-a-wallet  ... how else might it have been created?
• Does a private key need to be added for that wallet
• What is the relationship between the account "xeroc" and the wallet that was created?
• Are the terms "wallet" and "account" official Bitshares terminology? Where are they defined

I (naively) ran the code in the prologue of the pybitshares docs:

from bitshares import BitShares
bitshares = BitShares()
bitshares.wallet.create("secret-passphrase")
bitshares.wallet.addPrivateKey("<wif-key>")

And after being unable to unlock the wallet for a transfer:

from bitshares import BitShares
bitshares = BitShares()
bitshares.wallet.unlock("wallet-passphrase")
bitshares.transfer("<to>", "<amount>", "<asset>", "[<memo>]", account="<from>")

I found  a website that converts to and from WIF keys (http://gobittest.appspot.com/PrivateKey) and (naively) used that to create a wallet (unaware of this information on how to create a real wallet and add a WIF key given here - https://bitsharestalk.org/index.php?topic=26177.0).

So, now I am stuck with having created a wallet that is not truly on the bitshares blockchain.

I would like to completely erase the wallet I (naively) created. pip uninstall bitshares ; pip install bitshares did not get rid of the wallet I created but can no longer get in.
I would like to instead run the wallet creation code with the wallet I just created. There is a small problem though: when I went to wallet.bitshares.org to create the wallet, it seems that it was created as a sub-account of "floatation8" not as a full-account. The reason I say that is that the account I created (adsactlybot8) has no password - at no point in the account creation process was I prompted to enter a password for the new account. This I do not see how wallet.create('secret-passphrase') would work: is this passphrase supposed to be the same as the one when the wallet was created or a new one?

Here is a comparison table of pros and cons of the two approaches to wallet control:
https://docs.google.com/spreadsheets/d/1_Xt8ovZ6ouhGTjBiTmbcsvfT2RO4bPud3FArvwQFEZQ/edit?usp=sharing

Another thing is that by keeping all wallets internal, you have to do a lot of internal bookkeeping in terms of transactions. So instead of leveraging the blockchain to get all the atomicity right, you have to emulate that internally.

I've been working on the bitshare tip bot for a few days now:
https://gitlab.com/metaperl/btsbot

I basically hijacked the code for the https://github.com/bbedward/Graham_Nano_Tip_Bot and changed the wallet functions.

In working on the rain functionality, I have to say I echo the sentiment of the above users. It feels very fake to give people currency when you have not actually put it in their wallets. On the other hand, it does solve a usage issue: not being able to send someone something unless they register their bitshares username. And also, should a person never withdraw, you can simply reclaim the funds.

But the odd thing is there is no requirement for the person offering the rain to actually have any funds in the wallet.

Hello, I would like to get the following example from the PyBitshares documentation [1] to work:

   
    from bitshares import BitShares
    bitshares = BitShares()
    bitshares.wallet.unlock("wallet-passphrase")
    bitshares.transfer("<to>", "<amount>", "<asset>", "[<memo>]",
                        account="<from>")


Although this is not the meat of my problem, you cannot supply keyword parameters after positional parameters. Therefore the call to .transfer() cannot have account=<from> parameter at the end.

Anyway, moving on to the real issues, it seems that before you can get this example to work, you need to decide on a wallet operation model (Wallet Database, Provide Keys, Force Keys). For this discussion, I would like to focus on providing keys.

The Bitshares constructor [2] accepts a `keys` parameter whose value may be an array, dictionary or string. This leads to the following questions:

1 - what is a wif key? What does "wif" stand for?
2 - Where would I access the private key for an OpenLedger account? Please provide a precise navigation sequence.
3 - Where would I access the private key for a Crypto-Bridge account? Please provide a precise navigation sequence.
4 - Once I find the private key how does one supply it? The docs state the types of things that the `keys` parameter accepts, but it does not show how to supply it.

After looking at the wallet documentation [3] I have a few more questions:

1 - after adding a private key, does PyBitshares automatically know which Bitshares account it belongs to? For instance, if I add the private keys for the the bitshares user bev123 [4] am I able to call getActiveKeyForAccount [5] and supply 'bev123' as the name of the account?

[1] http://docs.pybitshares.com/en/latest/index.html
[2] http://docs.pybitshares.com/en/latest/bitshares.bitshares.html
[3] http://docs.pybitshares.com/en/latest/bitshares.wallet.html
[4] https://cryptofresh.com/u/bev123
[5] http://docs.pybitshares.com/en/latest/bitshares.wallet.html#bitshares.wallet.Wallet.getActiveKey

1. The preferred market pairing gives you the value(market cap) based on what you select. I selected bts(bitshares) so my UIA is valued in bts. This can be viewed in the overview section
2. Your UIA is paired with many other assets..BTC/STEEM/SBD/bitUSD/peerplays etc.
your users will just place orders in the desired trading pair
3. Currently we do not have tools to assist you in paying dividends. at the moment this must be done manually by you
4. Can it be deleted? I have not encountered a delete option. the information can be modified. i will see if i can get an answer for that
5. The Smart Coin allows for MPA's ( Market Pegged Asset)
yes, we can burn all the coins...i guess "deleting" goes against blockchain ideology.
hahaha