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

Pages: [1] 2 3
1
General Discussion / Re: I can't see my BTC in my wallet
« on: January 18, 2018, 04:48:48 pm »
You need to contact the operator of the BRIDGE or GATEWAY that you used. If it was Openledger.io GATEWAY that you used (Openledger (OPEN.X) then you can reach their support channel here: http://openledger.freshdesk.com/ or you can find their Telegram support channel here: https://web.telegram.org/#/im?p=@OpenLedgerDC

If it was a BRIDGE like Blocktrades.us, you will need to raise a support ticket / contact them on their website: http://blocktrades.us/

Any other provider (RuDex, Winex etc) you will need to contact them via their website.

2
Stakeholder Proposals / Re: Hardfork schedule proposal
« on: August 15, 2017, 06:26:21 pm »
I'd like to bring to your attention BSIP-0022 (https://steemit.com/bitshares/@cm-steem/bsip-0022-draft-introducing-expiring-votes-for-witnesses-committie-members-and-proxies-within-the-bitshares-network-an)

It would be extremely useful to have this functionality in the next hard fork so that active accounts have a better chance of being considered in any votes.

3
Technical Support / Re: Bitcoin withdrawal
« on: July 16, 2017, 06:22:59 pm »
How did you withdraw them? Did you use Openledger gateway or the Blocktrades bridge? If you used Openledger then you need to contact their support at support@openledger.info with your Bitshares username and the Bitcoin address you sent your Bitcoin too.

4
General Discussion / Re: Paying Employeess In Nigeria With Bitshares
« on: June 29, 2017, 01:20:32 pm »
One way would be to pay them in Bitcoin first - to make sure they can find an offramp (Bitcoin has a fair few - nearly a decade of existence buys you that much market penetration). Then, ongoing you can pay them in BitUSD and they can exchange it to Bitcoin whenever they want to offramp. There are gateways in the wallet for super-simple conversion from bitUSD/BTS/Other DEX assets ->Other cryptos (like Bitcoin).

5
General Discussion / Re: Bitshares State of the Network Report
« on: June 29, 2017, 01:13:12 pm »
My bad - I've updated the post to reflect the correct link: https://eos.io


6
General Discussion / Re: Bitshares State of the Network Report
« on: June 28, 2017, 07:34:31 pm »
Bitshares and EOS are different platforms. EOS is designed to be a generalized smart contracts platform like Ethereum, but borrowing some of the concepts from Bitshares and Steem (both were founded by Dan Larimer who is building EOS).

So, in answer to your questions; If you want to be part of EOS, you need to hold EOS tokens. Holding Bitshares does not entitle you to any share of EOS. EOS is using the Ethereum platform to distribute tokens, so you can buy some Ethereum and then send them to a special address and this will reserve you some EOS tokens. See https://eos.io for details. EOS tokens *may* at some point in the future also be available on the Bitshaes DEX (Distributed EXchange), probably via a gateway like OpenLedger.io (https://openledger.io)

Second question; Although EOS was built by the same guy that built Bitshares, its not clear (yet) what concepts (if any) will be applicable to Bitshares. There are lots of discussions going on in Bitshares development circles about how Bitshares and EOS may interact (or Bitshares may enhance itself with new technologies being built for EOS), but since EOS hasn't actually been built yet it's a bit early to know. Certainly, in the past Bitshares has benefited from developments on other platforms like Steem (Not Steam) for example, so time will tell... 


7
OpenLedger / Re: CCEDK verification
« on: June 20, 2017, 11:34:03 pm »
It they are not getting back to you in a timely manner - and I'd assume that pretty much this is a running theme with most crypto-currency exchanges at the moment given the huge influx of new participants - you may want to register and get verification on a number of other exchanges that support other crypto-currencies like Ethereum or Bitcoin but may not directly support Bitshares (BTS), buy one of these intermediaries (E.g. Bitcoin) and then exchange it to Bitshares (BTS) through either one of the exchanges  (Like Poloniex which has a BTC/BTS or ETH/BTS pair) or use one of the Gateways to perform the instant conversion of BTC/ETH/{A NUMBER OF OTHER COINS} to BTS. A list of your options are available here: https://bitshares.org/deposit/

Possible intermediary exchanges you could consider in no particular order:

  • Kraken
  • GDAX
  • Coinbase
  • Bitstamp
  • Coinfloor
  • Gemini
  • LocalBitcoins
  • Bittylicious
 

8
Technical Support / Re: Can I access public nodes in CLI_wallet?
« on: June 19, 2017, 10:15:04 am »
Any core dev's have any thoughts?

9
Technical Support / Re: 0.9.3c unable to lock file by block1 when rebuilding index
« on: June 14, 2017, 08:53:20 pm »
These steps may help (courtesy of Ar3s701 on reddit)

Just recovered my Bitshares X and there was a few parts not covered in the migration guide.

Scenario: I had Bitshares in the old Bitshares X client (0.4 or whatever) and a backup from that wallet that I wanted to migrate to Bitshares 2.0.

  • Installed my old Bitshares X client.
  • Imported/Recovered my old wallet.
  • Went into the console and ran the command "wallet_dump_private_key" to get my private key from Bitshares X. You'll need this in the next few steps.
  • Installed Bitshares client 0.9.3c and downloaded the Legacy Blockchain. Note that it took about an hour or more of it to resync after adding in the legacy blockchain.
  • Add in your account to client 0.9.3c. Since there was nothing for the client to sync to and importing my wallet kept telling me I had the wrong password, I added the name of my account from bitshares x and then I was able to claim it with my private key I exported earlier.
  • You need to resync again before you'll see your balance. It takes a long time but not as long as the first time. (Goto account list->advanced settings->console and run rescan)
  • Now we can finally run the command that we need. wallet_export_keys C:\Users[your user name]\Desktop\keys.json
  • Now that you have your keys, you can claim your lost bitshares. I was able to claim them on the online wallet https://bitshares.org

Once you've reclaim, make more backups.

10
Technical Support / Re: Can I access public nodes in CLI_wallet?
« on: June 14, 2017, 05:42:30 pm »
I've just tried this and I get the same, regardless of which web-socket server is used. This is on Bitshares Core release 2.0.170606 on Windows, using
Code: [Select]
cli_wallet -s {any-websocket-server}
The error:

Code: [Select]
C:\Temp\bitshares-cli>cli_wallet  -s  wss://dexnode.net/ws
Logging RPC to file: logs\rpc\rpc.log
2220742ms th_a       main.cpp:120                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
2220742ms th_a       main.cpp:124                  main                 ] nathan_pub_key: BTS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
2220742ms th_a       main.cpp:125                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
2220757ms th_a       main.cpp:172                  main                 ] wdata.ws_server: wss://dexnode.net/ws
0 exception: unspecified
TLS handshake failed
    {"message":"TLS handshake failed"}
    asio  websocket.cpp:518 fc::http::detail::websocket_tls_client_impl::{ctor}::<lambda_79cc34a518286825a5be07605053c212>::operator ()

    {"uri":"wss://dexnode.net/ws"}
    th_a  websocket.cpp:704 fc::http::websocket_client::secure_connect

    {"uri":"wss://dexnode.net/ws"}
    th_a  websocket.cpp:678 fc::http::websocket_client::connect


I've also tried a number of web-socket servers from the light client as well as the one in the documentation: wss://bitshares.openledger.info/ws

Also, where are the log files stored? It says logs\rpc\rpc.log - but where is that as it doesn't seem to be rooted in the folder the cli_wallet executable is called from?

11
Stakeholder Proposals / Re: Proposal: Bounty for famous person $xxxxUSD to review BitShares
« on: June 10, 2017, 01:12:30 pm »
I wouldn't waste the money. The rising interest in Bitshares will eventually bring a corresponding stream of editorial coverage, even if the current explosive growth rate is mediated by a fall at some point in the near future.

Bitshares is a solid platform. It's not perfect, but it's probably the best most forward thinking platform in the crypto-space and the technology and the features should speak for themselves.

Besides, if you pay for a review it won't garner nearly as much respect as one that was written organically. 

12
Technical Support / Re: Stealth Transactions - Any ETA?
« on: July 07, 2016, 11:54:56 am »
Certainly reassuring. By making Bitshares more palatable, more investment is likely to flow into it, increasing the value of BTS and indirectly repaying the STEALTH transactional costs. Even 1/10th of Ethereum adoption - which doesn't have working pegged smartcoins as far as I know or such a high theoretical transaction count (tMAX)  - would yield huge rewards.

Back on the topic at hand - how much of this documentation actually works/applies: https://bitshares.org/doxygen/group__stealth.html ?  I know some STEALTH transactional features were implemented by Cryptonomics but it is unwieldy and/or incomplete. Is there a need to wait for updated documentation regarding STEALTH transactions before it can be considered production ready and implementable in third party wallets/clients?

13
Technical Support / Re: Stealth Transactions - Any ETA?
« on: July 06, 2016, 10:28:36 am »
Will it be expensive relative to a normal transaction? STEALTH is a critically important feature and really should be the default rather than the exception. The idea that everything is on display for everyone is just very difficult to sell. You get significantly more privacy from a traditional banking relationship.

14
Technical Support / Stealth Transactions - Any ETA?
« on: July 05, 2016, 03:17:00 pm »
Is there any ETA on some form of workable stealth transactions for Bitshares to obscure either the amounts and/or the transaction participants? Being able to enter poloniexwallet (the Bitshares wallet of the exchange Poloniex) and see their entire balance and transaction history is just such a huge barrier when selling or developing for the Bitshares platform, which otherwise is pretty great. 

15
Technical Support / Re: Bitshares Account Setup for centralised website
« on: March 04, 2016, 06:18:02 pm »
Quote from: abit on March 04, 2016, 05:43:23 pm
Make your own GUI, make the memo field and to field readonly (or hidden)

What do you mean? How does that work if I'm sending funds from - for example - the Bitshares Android Wallet?

Quote from: cube on March 04, 2016, 05:50:42 pm
One other possible way:
D) Your website create a customer code for each customer and register their customer code in the blockchain. 

That's very interesting and a distinct possibility. Do you have any documentation/api method pages you could point me to?

Pages: [1] 2 3

Page created in 0.023 seconds with 23 queries.