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.


Messages - ElMato

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 20
46
General Discussion / Re: Lowering Transfer Fees
« on: October 21, 2015, 07:52:25 pm »
What happens if we set (as a registrar) the network_fee_percentage to 100%

Will the users registered by this registrar only pay $0.04? and nothing to the registrar?

47
General Discussion / Re: Witness Alerts and Status
« on: October 21, 2015, 07:37:03 pm »
ElMato Updated
Blockchain replayed automatically because of db upgrade.
Done reindexing, elapsed time: 37.57736299999999829 sec

48
General Discussion / Re: Fee Adjustments
« on: October 21, 2015, 01:12:37 pm »
Even if we can resolve this by just voting, the different perspectives shown in this thread work in people minds to enrich their decisions.

I do agree that we need to be profitable as a DAC and fees play an critical role.
I also don't have the scientific proof that if we lower the fees transfers will climb.

(Maybe there is no high amount of transfers because we are not ready (yet) for mainstream users, and bitcoiners don't like us much (yet) ) 

Having said that $0.2 USD transfer fees make some project unviable.

Im pushing Bitshares for a joint effort of two NGOs and the local crypto community which one the objectives is to provide entrepreneurs from marginal economies with a way to use digital cash. (Its a bigger project ex-Worldbank, ex-UN people working on it)
 
Basically they will be moving an IOU, but $3.2 ARS is too much for the average size of that transactions. ($30-$50)

One of the founders of http://www.rootstock.io/ is heavily involved in the project also, so that platform is on the table also even if its on alpha stage.

Another issue is the order placement fee in the DEX, but i read that with lifetime subscription the fees goes down to something like 2 BTS? So that will be fine to bootstrap the DEX.

49
Stakeholder Proposals / Re: Lets vote for lower fees!
« on: October 18, 2015, 10:19:10 am »
Quote from: alt on October 18, 2015, 12:40:21 am
guys, you are OK with the current fee.
but in fact, Chinese and other developing country will never accept the high transfer fee.
In China we spent no fee with alipay and most  bank card.
BTS will lose these market if the fee still keep about 0.6CNY
If you don't care about these market, OK, just keep higer fees. wish enough American like BTS and can be a real user.
+5%

Here in Argentina:
* Free bank accounts (no CC, just saving)
* No transfer fees (below 30K ARS)
* Instant transfers

50
General Discussion / Re: why I cannot send BitCNY in 2.0
« on: October 18, 2015, 04:27:33 am »
The fee pool is empty, thats why you cant send bitCNY.

I filled with 200 BTS to allow for ~10 txs.
I don't know how is in charge of fill these pools (?)

This is the cli command to fill.
 
fund_asset_fee_pool [ACCUONT_NAME] CNY 200 true

51
General Discussion / Re: why I cannot send BitCNY in 2.0
« on: October 18, 2015, 12:31:25 am »
It seems that the fee pool is empty.

Who is supposed to fill these pools?

52
Technical Support / Re: Margin Call Price
« on: October 17, 2015, 08:31:52 am »
I think we fix it

53
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 15, 2015, 07:26:54 pm »
elmato updated to latest branch "bitshares" and replayed.
(everything works fine)

54
General Discussion / Re: Witness Alerts and Status
« on: October 14, 2015, 09:10:07 pm »
Telegram group (plus spartako_bot) is working really good for witness coordination.
I'm already in. 

55
Technical Support / Re: Forcing API users to authenticate over websockets will hinder adoption
« on: October 14, 2015, 07:00:36 pm »
@monsterer I agree with you, authenticated http access should be available.

For the time being i'm using a little hack in
https://github.com/cryptonomex/graphene/blob/29cc90ba99b3e317ced330a90f502e33c4f59f1f/libraries/app/application.cpp#L173
Code: [Select]
         _websocket_server->on_connection([&]( const fc::http::websocket_connection_ptr& c ){
            auto wsc = std::make_shared<fc::rpc::websocket_api_connection>(*c);

            auto login       = std::make_shared<graphene::app::login_api>( std::ref(*_self) );
            auto db_api      = std::make_shared<graphene::app::database_api>( std::ref(*_self->chain_database()) );
            auto network_api = std::make_shared<graphene::app::network_broadcast_api >( std::ref( *_self ) );
            auto history_api = std::make_shared<graphene::app::history_api >( std::ref( *_self ) );
            auto node_api    = std::make_shared<graphene::app::network_node_api >( std::ref(*_self) );

            wsc->register_api(fc::api<graphene::app::database_api>(db_api));
            wsc->register_api(fc::api<graphene::app::login_api>(login));
            wsc->register_api(fc::api<graphene::app::network_broadcast_api>(network_api));
            wsc->register_api(fc::api<graphene::app::history_api>(history_api));
            wsc->register_api(fc::api<graphene::app::network_node_api>(node_api));
         });
 
This will give you deterministic api number:
database_api = 0
login_api = 1
network_broadcast_api = 2
history_api = 3
network_node_api = 4

Long term solution:
 * Put HTTP headers in websocket_connection
 * Validate user/pass, give access to api based on api-access
 

56
Stakeholder Proposals / Re: Proxy: fav - Journal
« on: October 14, 2015, 01:48:12 pm »
Quote from: fav on October 13, 2015, 10:19:30 pm
Elmato, wackos you both participated in the testnet, right?

Sure!
Some proofs here
https://bitsharestalk.org/index.php/topic,17962.msg240093.html#msg240093
https://bitsharestalk.org/index.php/topic,18751.msg241827.html#msg241827

57
Stakeholder Proposals / Re: Proxy: fav - Journal
« on: October 13, 2015, 10:10:07 pm »
@fav would you like to add elmato to your list?

58
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 13, 2015, 05:21:22 pm »
elmato ready
get_witness elmato
{
  "id": "1.6.20",
  "witness_account": "1.2.31489",
  "last_aslot": 0,
  "signing_key": "BTS7TrF5cDX66egLWPLJ7YCnZD5vHeFTgNbPChV8MDQnVKMzDfPrK",
  "vote_id": "1:30",
  "total_votes": 0,
  "url": "http://about:blank",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

59
General Discussion / Re: [ANN] LimeWallet - Beta
« on: October 13, 2015, 01:58:02 am »
@cass, that will be great.
Can you do it?

60
General Discussion / Re: [ANN] LimeWallet - Beta
« on: October 12, 2015, 11:41:05 pm »
Quote from: kenCode on October 12, 2015, 05:44:10 pm
Not sure why, but the friend who sent me the 1 bit€ actually shows in my Limewallet as "€ 1.0013 Received".
Weird.
Known bug with unregistered accounts.

Quote

Now, I wanted to empty my Limewallet before the next upgrade, so I went to the Send screen.
I typed in 1.00 to send, filled in a valid Recipient name, it allowed me to select the proper account from a list, I typed in a short textual memo and clicked on the Send button at the bottom. The button blinked, but does not do anything.
Weird.
 
I clicked the Send button at the bottom again, it blinked but did nothing (no error message either).
Weird.
 
So I figured I was trying to send too much. There is nothing telling me the max amount that I can send, with fees.
Weird.
 
I changed the 1.00 to 0.95 then clicked on the send button at the bottom again and bamm it gave me a popup confirmation, i accepted it and it then showed me the confirmation screen.
 
The funds showed up almost immediately in my linux client wallet. Very cool. :)
 

Known bug not telling that there is no enough balance.

Quote
Now, back at the main Limewallet screen, it still says I have a € 1.00 balance, and the transaction I just sent does not show in the list below called "THIS MONTH".
Weird.
 

The WebSocket notifier is down, so its not automatically refreshing.
You need to manually refresh (pulling down on the transaction list) or restarting the app.

Quote
Just a few weird things, thought I should report them here too so you know what I am looking at. I LOVE this wallet and see great things here!! :)

Thanks for reporting Ken, now we are full steam ahead to support the bts2 backend.

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 20

Page created in 0.201 seconds with 23 queries.