Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - monsterer

Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13
121
Technical Support / does wallet_import_private_key add to the list of private keys or replace?
« on: January 17, 2015, 08:57:19 pm »
Using wallet_import_private_key, does this add the key to a list for the account, or overwrite the current key?

122
Technical Support / Does wallet_burn decrease the current supply of a UIA?
« on: January 17, 2015, 02:59:59 pm »
If I create a UIA, does burning it decrease the current supply of the asset as reported by get_asset?

123
Technical Support / Possible to get active key of unregistered account from a transaction?
« on: January 17, 2015, 02:15:46 pm »
If an unregistered account sends me a transaction, is it possible to get their currently active account key?

124
General Discussion / DEX Arbitrage to increase liquidity
« on: January 16, 2015, 05:18:43 pm »
If there were markets in the DEX which enabled internal arbitrage, it could help with providing liquidity and narrowing spreads.

For example, if we had the pairs:

btc/usd
btc/eur
eur/usd

You would be able to do triangular arbitrage between them which would narrow the spreads and be less risky than running a market maker.

Cheers, Paul.

125
Stakeholder Proposals / Increase the memo field in the transaction to 64 characters
« on: January 15, 2015, 09:07:15 am »
That way a memo can reference a bitcoin address, or bitcoin TXID as well as bitshares trxid and account name.

The current length cant even accommodate a bitcoin address.

use case: gateways - having the user put their desired bitcoin address into the memo field of a bitshares transaction removes the need to import private keys into the bitshares wallet, which is fragile and only works once due to change addresses.

126
Technical Support / Automatically refunding transactions sent from unregistered accounts?
« on: January 15, 2015, 08:40:49 am »
I can refund a transaction from a registered account by looking at the from_account field, which is their account name. An unregistered account has a stealth public key in place of the account name - so, how do I know where to send the refund?

127
Technical Support / Transaction sent to unknown public key
« on: January 13, 2015, 08:36:43 am »
For my gateway testing I've created an unregistered account on my spare lap top. To fund it, I had to add its public key and account name to my main wallet. This all worked fine.

However, when trying to send funds to this account I get a transaction ledger entry which shows the funds didn't go to the correct public key at all.

From account: BTS7usxZ6jKRptKTr3gAZEhgxceoBBvT7ZmrVxZ2b8LPrYfz4Lsib (pay.monsterer)
To account:BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB (gatewayclient)

The wallet GUI shows this transaction as being sent fine. However it never turned up on the gatewayclient wallet. Calling wallet_get_transaction 9076cce58527d0b92f65b74f9c405c0cb1b733df results in this:

Code: [Select]
"ledger_entries": [{
      "from_account": "BTS7usxZ6jKRptKTr3gAZEhgxceoBBvT7ZmrVxZ2b8LPrYfz4Lsib",
      "to_account": "BTS5dvyrpghWB9vmcZtcJVWJtYhLCQ4S8ptriskuLv45Qqi4FDe8X",
      "amount": {
        "amount": 100000,
        "asset_id": 0
      },
Notice the to_account is not correct?

Any idea what has happened here?

Cheers, Paul.

128
General Discussion / Reversible transactions - is there any sane way this could work?
« on: January 08, 2015, 04:47:54 pm »
Seems to me that nearly every bitcoin theft/heist in history could have been easily circumvented if transactions were somehow reversible.

The trouble is, how do you implement this feature in a sane way? Having both parties agree to reverse the transaction is one way, but that doesn't help for thefts.

What about somehow allowing transactions (or even a special transaction type) to be reversed by delegates, or even reversed by majority vote?



129
General Discussion / Want to put an ad for bitshares on my blog, but the logo isn't compelling enough
« on: December 17, 2014, 09:49:44 am »
Do we have something that at least contains a tagline or hook as well as the bitshares text?

130
Technical Support / wallet_asset_transfer 0.1 BTS <from_account> <to_account> actually sends 1.0 BTS
« on: December 16, 2014, 09:43:10 pm »
Code: [Select]
wallet_transfer 0.1 BTS pay.monsterer monsterer

{
  "index": 0,
  "record_id": "21d584ced7419c44ff9260236f68f461ff0c6302",
  "block_num": 0,
  "is_virtual": false,
  "is_confirmed": false,
  "is_market": false,
  "trx": {
    "expiration": "2014-12-16T22:45:05",
    "delegate_slate_id": null,
    "operations": [{
        "type": "deposit_op_type",
        "data": {
          "amount": 100000,
This is in v0.4.26.

131
General Discussion / [MetaExchange] dev-metaexchange.monsterer development diary
« on: December 15, 2014, 08:37:26 pm »
Hi all,

Shentist and I thought it would be good to set up a development diary for the progress we are making on Metaexchange, which is being funded by our 100% pay delegate, dev-metaexchange.monsterer.

https://github.com/wildbunny/metaexchange

The first task on this project is to produce a daemon to enable anyone to set up a bitcoin on-ramp into bitshares.

The idea is for the daemon to convert bitcoin deposits into bitAssets directly, so users can send bitcoin to a special address which is monitored by the daemon and have the daemon issue the corresponding quantity of bitAssets and send them directly to the depositor, thereby enabling an easy route into (and out of, using the reverse technique) bitshares.

Progress so far has been good, I have the first part of the code for scanning the bitshares blockchain in place, for picking out the public key of the depositor, and converting that into a bitcoin address. I also have unit tests for going to and from bitcoin and bitshares public keys and addresses.

The next step is to work on the bitcoin blockchain scanning portion of the code, which will be easier than the bitshares side, since all the RPC data structures already exist and so I expect that to go smoothly.

If you have any questions, I'd be happy to answer them!

Cheers, Paul.

132
Stakeholder Proposals / [Proposal] - review of new bitshares build testing procedures
« on: December 12, 2014, 12:19:02 pm »
In light of the recent 'problems' with the accidental hard fork in v0.4.25, I propose that new builds are not pushed to live until a test delegate has run them for 24 hours and confirmed they are still on the main chain with no failures, or memory problems.

These recent problems could have been avoided if such measures were in place.

133
Technical Support / Are the lowest possible units in every asset called 'Larimers', or just for BTS?
« on: December 11, 2014, 04:32:10 pm »
Just for the record, is there a name for the lowest possible unit of an asset, given that they're all different potentially?

134
Technical Support / Best way to tell if transaction is a deposit via RPC?
« on: December 09, 2014, 11:18:46 am »
I'm trying to find the best way to determine whether a given transaction is a deposit.

Using wallet_account_transaction_history, we have a structure returned which contains multiple ledger entries and I'm not sure if you could have both a deposit and a withdraw inside that array?

Using blockchain_get_transaction we have an array of 'operations' inside the 'trx' field which typically contains both withdraw_op_type and deposit_op_type.

Is there an easy way to tell whether a given transaction is a deposit? Just some clarity on the subject would be great :)

Cheers, Paul.

135
Stakeholder Proposals / avoiding delegate downtime while upgrading client
« on: December 08, 2014, 04:22:44 pm »
What is the best way to avoid delegate downtime while upgrading the bitshares client?

Is there a way to know when you've just produced a block, to give you maximum time before your turn comes around again?

Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13

Page created in 0.143 seconds with 15 queries.