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 - Mateusz

Pages: [1] 2
1
Stakeholder Proposals / Re: [Poll] BAIP6: BTS-DEX economic model
« on: May 25, 2020, 07:04:29 pm »
BAIP6(https://github.com/bitshares/baips/blob/master/baip-0006.md) is a new drafted proposal that consist of the updated Market Making contest(Ordering Mining) rule and some other parts, the purpose is to cultivate the market depth and the trading activeness in BTS-DEX through a task distribution mechanism, and to increase the system income to buy back BTS to create value for BTS stake holders.

Now 2 poll workers have been created:

1.14.260 Poll-BAIP6-Implement BTS-DEX economic model
1.14.261 Poll-BAIP6-Do Not Implement BTS-DEX economic model

According to BAIP procedure definition, the BAIP6 will be considered approved while below 3 criteria are met:

1.worker 1.14.260 get more voting power than 1.14.261 worker.
2.worker 1.14.260 get more voting power than BAIP-Threshold Worker 1.14.236.
3.Both No.1 & 2 above last for three consecutive days.

Kindly Reminder:

BTS-DEX try to make sure,but do not guarantee that the listed gateways always provide liable service and is not legally responsible for that, users need to judge the service liability of the gateways by him/herself.

As RuDEX and XBTSX claimed not to participate the subsequent Ordering Mining, at the beginning only GDEX is included in the gateway list,  however any qualified gateway is welcomed to join after the Ordering Mining begin if the gateway accept the mentioned conditions in the BAIP.

Please vote according to your opinion.

Placing additional burden on the actual value creators in the network, especially in this hard time, is irrational. This is another attempt in a series of failures at financial engineering and makes further -90% drop in the price of BTS likely. How much more money do you need to lose before you admit failure and reverse course? Rejected.

2
General Discussion / Re: BlockPay in Serious Trouble
« on: June 09, 2017, 12:31:41 pm »
With Bitshares value where it is today and given the troubles with Blockpay, is it not possible for a worker to fund the development of stealth?  That way everyone pays and everyone benefits.  Lets move on asap and get it built.
Only those that hold STEALTH benefit .. and that is mostly dan (who had the foundation coded) and kencode .. no one else has any incentive to work on stealth the way it is right now

That is besides the BitShares Munich IVS that took money for the development of Stealth and transferred rights to "the stake in the revenue stream from it's products" to the BLOCKPAY token holders. If the CEO were to find himself in a bind that he's unable to solve, he should step down and take his case to the shareholders and the community as the common courtesy dictates. The deliberate opaqueness and unwillingness to debate the situation openly tells it all.

As for the failing price of the BLOCKPAY token I hold the CEO directly responsible.

3
Yes, please! The more coins the merrier.

4
General Discussion / Re: BlockPay in Serious Trouble
« on: June 09, 2017, 07:24:24 am »
No PR whatsoever, the only developer and co-founder has been suspended until further notice and the minority shareholder and CEO thinks he can strong-arm the majority shareholder. Correct me if I'm wrong but it seams to me, it's high time to salvage anything that is left from BlockPay project and move forward under the OpenPOS brand.

6
Two questions.

1. You've used Bitshares code base so it is only fair to sharedrop a part of your tokens on the Bitshares community. How big a share, in terms of a percentage, is the original Bitshares 2.0 code worth compared to your entire business as is?

2. Will GXShares and GXCoins be listed on BitsharesDEX?

7
Technical Support / Re: Failed to sync with the API server
« on: September 05, 2016, 10:12:34 pm »
After updating the API connection menu showed up. Many thanks!

8
Technical Support / Failed to sync with the API server
« on: September 05, 2016, 09:04:55 pm »
I recently downloaded the new BitShares 2.0.160813 light software and set up my account. All seamed to be working flawlessly until yesterday when I tried to start the client and got the following screen:

Quote
Failed to sync with the API server
Please verify that your computer clock is correct.
Once you've synchronized your clock, please refresh this page.

I live in the UTC+1 time zone and use Windows 7 x64 with clock automatically synchronized with 'time.windows.com'. I've synced the computer clock and restarted the client multiple times but the problem persists. How do I change API server or otherwise resolve this error?

9
General Discussion / Re: How to move your account to another wallet?
« on: March 15, 2015, 01:59:30 pm »
I don't believe so. There is a difference between a wallet and an account:

Quote
Account: An account is similar to a deposit box and should be registered on the blockchain
Every transactions to your account name is sent to an address which is
controlled by a derived key from the account private key

Wallet: The wallet is a set of account names and corresponding private keys.
When you first created an account name, the private key for that account key
is derived from the wallet private key and can thus be recalculated from the wallet private key.

What I'm essentially asking is if it's possible to decouple a registered account from the wallet file and transfer it into another, newly created wallet file.

10
General Discussion / How to move your account to another wallet?
« on: March 15, 2015, 01:13:18 pm »
Hello, in order to split the risk and diversify my funds I wanted to move my registered account name and all funds associated with it to another wallet file. Is it possible with BitShares and if so, what is the process?

11
General Discussion / Re: Cannot recover wallet backup
« on: February 18, 2015, 08:42:45 pm »
After installing version 0.6.1 I used the "File -> Import Wallet" menu multiple times trying to import the JSON backup file. Each and every time it failed resulting in Error: invalid password (20001) notification, although the password was correct. The JSON backup file was created using Bitshares X software version 0.4.7.

12
General Discussion / Re: Cannot recover wallet backup
« on: February 17, 2015, 09:53:16 am »
Positive! That worked. I've just downloaded version 0.5.3, imported the wallet file, updated to version 0.6.1 and now all is syncing again. You guys need to fix that. By the way the GUI in earlier versions was much neater and easier to use. Thanks!

13
General Discussion / Cannot recover wallet backup
« on: February 16, 2015, 09:28:37 pm »
Hello, in August last year I downloaded the Bitshares X software and registered my account. After that I backed up the JSON wallet file on external thumb dive. Recently I wanted to access my account and therefore I downloaded the latest Bitshares software version 0.6.1. After installation I tried to import the wallet but received an error notification: (...) Error: invalid password (20001). Since I wrote the password down in my notebook I was sure that the password is right, but the software keeps rejecting it. What are my options in order to regain access to my account or retrieve or break the password to the backup file?

14
Technical Support / Re: BTSX Wallet is Not Syncing
« on: August 25, 2014, 07:13:39 am »
I've restarted computer and all is working fine now. Thanks!

15
General Discussion / Bitshares FOREX trading impractical?
« on: August 25, 2014, 04:06:31 am »
Please someone explain to me who is going to trade FOREX using Bitshares blockchain, taking into consideration how narrow the profit margins for intra fiat currency trading are, moreoever with the requirement of holding twice the reserves on the account.

Pages: [1] 2