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

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 64
31
General Discussion / Re: Today's wallet seems to be very not smooth
« on: February 17, 2016, 04:00:11 am »
What are the steps to setting up a wallet?

git clone https://github.com/bitshares/bitshares-2.git
cd bitshares-2
git checkout 2.0.160216
git submodule update --init --recursive
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTS=OFF .
make
cd programs/witness_node
./witness_node

git clone https://github.com/bitshares/bitshares-2-ui.git
cd bitshares-2-ui
cd cli; npm install
cd ../dl; npm install
cd ../ios; npm install
cd ../web; npm install
npm start

Comment if you run into issues, but that's the basic process...

32
General Discussion / Re: Today's wallet seems to be very not smooth
« on: February 16, 2016, 04:01:45 pm »
Finding the reason would be easier if you provided more details.  Are you using a hosted wallet instance, or where are you accessing the wallet?  Are you having issues loading the entire page, or is slow navigation within the wallet the problem, or is it just not updating responsively with data from the chain?

33
His entire case is based on the idea that the political and economic spheres are currently separated, which they are not.  He also never defines "capitalism", and it doesn't seem he knows what it means.

34
General Discussion / Re: Today's wallet seems to be very not smooth
« on: February 16, 2016, 03:35:41 pm »
BitShares 2.0.160208 seems fine to me running locally.  Any particular areas you're noticing issues?

35
Technical Support / Re: Unlinkable block error when syncing
« on: January 31, 2016, 05:31:08 am »
Got synced.  I re-checked out the latest tag and rebuilt (again) in RelWithDebInfo mode.  Not sure if I wasn't really on latest before or if something else was going on, but thanks.

36
Technical Support / Unlinkable block error when syncing
« on: January 30, 2016, 08:24:30 pm »
I've attempted to resync a number of times today and keep stalling out with this:

Code: [Select]
1270591ms th_a       application.cpp:525           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:81 _push_block

    {"new_block":{"previous":"002ed047b2c977366e45ec5164ae95d2ae84bb97","timestamp":"2016-01-29T01:37:33","witness":"1.6.17","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"204303bc91c8cb28cdcc38575ec9547f0dc4970170b831683c75f1f0abbf92d48136505af995804ab9bea416a5f90afe96b7db762fc2dfc033f36083416b9f4d47","transactions":[]}}                                                                                                         
    th_a  db_block.cpp:201 _push_block
1270591ms th_a       fork_database.cpp:60          push_block           ] Pushing block to fork database that failed to link: 002ed049662d95b06d7e8164b27e204b113511ba, 3067977
1270591ms th_a       fork_database.cpp:61          push_block           ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe
1270591ms th_a       application.cpp:525           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:81 _push_block

    {"new_block":{"previous":"002ed0480aea3c92bd537999d865cc7cb3c0a54e","timestamp":"2016-01-29T01:37:42","witness":"1.6.35","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f5d8a0a03d97498a1d501e39510cec4e92d3db093d5e24cba4b3ab5b09b5661a764686113e417c2753377c6bb7f77d0a39af0231f67ed7fda285477f52145697f","transactions":[]}}                                                                                                         
    th_a  db_block.cpp:201 _push_block
1270591ms th_a       fork_database.cpp:60          push_block           ] Pushing block to fork database that failed to link: 002ed04a061430c5daec0f233e6b2147e05d0768, 3067978
1270591ms th_a       fork_database.cpp:61          push_block           ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe
1270591ms th_a       application.cpp:525           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:81 _push_block

    {"new_block":{"previous":"002ed049662d95b06d7e8164b27e204b113511ba","timestamp":"2016-01-29T01:37:45","witness":"1.6.49","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f71078310ac9dcff2b706d275e3b365d4a6637d00da692d1b5c9be87ca708200307fe0e61ccf1a82dc92472442377ad6be2d8d4e163fd5b66ee5042c369828912","transactions":[]}}
    th_a  db_block.cpp:201 _push_block
1270592ms th_a       fork_database.cpp:60          push_block           ] Pushing block to fork database that failed to link: 002ed04bb1ee8f9843fed2aa9054f76bf75425a1, 3067979
1270592ms th_a       fork_database.cpp:61          push_block           ] Head: 3067959, 002ed0373fd510a23b375e022c62154499b35bbe

Any ideas?

37
Status Update

Those of you mining may have noticed that payouts have gone past the threshold that we set for the pool. This is due to cryptsy delaying the transfer of BTC out of their exchange. There have been a whirlwind of other accusations related to cryptsy payouts including class actions.

Some of our more profitable coins were only on cryptsy, but there isn't more profit when you simply are not getting paid out.

I decided that we would cut our losses, and use what coins we can, and a few new ones that we can exchange at Poloniex, and Bittrex.

Between these two exchanges, we currently have about 17 coins between all three algos that the pool currently supports. In addition to this, we also have enabled merge mining with DOGE. We are working out a way to make this part of the bonus payout.

The migration has not been completed yet. As you can see, after we had updated all the wallets and the config for the pool it appears all our charts suddenly stopped working. This has been reported to @Freebieservers along with the updated deposit addresses to start being directed at the other exchanges. If you ignore the charts you can see from the workers below on the Dashboard the current coins that are being mined.

Hopefully we will see the payout make its way out of crytpsy, but we aren't holding out a lot of hope given all the accusations and the shrinking volume happening there.

Please continue to test the pool and report any other issues you are finding, or things missing that you think should be there in regards to features and/or reporting. If you have been mining elsewhere while we are still in development and have seen some good success with other coins, also feel free to share and we can consider adding those to the pool if they are available for exchange on Polo/Bittrex.

Isn't this on opportunity, if several of the most profitable (demanded) coins now have no exchange?  Why not hang on to them and issue corresponding UIAs to set up a gateway?  You could reach out to their communities and let them know, since I'm sure they're looking for a new exchange.

EDIT: Perhaps @monsterer, @dannotestein, or @ccedk could help out with that...

38
General Discussion / Re: Millions of Features, Features for Me!
« on: December 11, 2015, 11:59:59 pm »
So to get this started, please place your bids for the MAKER asset which will earn 20% of all liquidity incentivization rewards if the Liquidity Incentivization proposal is approved and executed.  Lets see how the community actually values this potential feature and then move on from there.

Where do we place our bids, and are you including @Chronos counter proposal to make it fair?

This.  Should bids be in BTS, BitUSD, BitCNY, or will Cryptonomex fill orders across several markets?

39
What's up with X11?

Sorry can you be more specific? What kind of issue are you having with x11?
No one is getting payouts, and the payout estimates are all at almost nothing.

40
What's up with X11?

41
What's the status on X11?  I've been mining at ~8MH for a few days and I'm showing "Est. Value Payout: 0.00015 BTS"...

42
Since most of their focus is off chain it may make sense for the AMP token to live on the BitShares chain natively.

43
General Discussion / Re: LTC Dumped on OKCoin -
« on: November 10, 2015, 02:57:30 pm »
And it's another argument for decentralized exchanges and low reliance on each gateway.

44
Technical Support / Re: No Affiliate System at launch
« on: November 04, 2015, 03:11:18 am »
Yeah... well using https://bitshares.openledger.info?r=(your account name here)   so how I did it was https://bitshares.openledger.info?r=bitcoin42  the fee allocation looks like this:

Fee Allocation
Network   20%
Lifetime Referrer   (bitcoin42)   30%
Registrar   (openledger-reg)   20%
Affiliate Referrer   (bitcoin42)   30%


How can I become the Registrar? I tried to create an account from the light wallet, and then extract the private key of that account and import it into a new wallet, but that didn't work. Any ideas?

To be the registrar you have to be the one to actually create the account and pay the creation fee.  I think the only way right now is using the CLI wallet or running your own faucet server.

45
Technical Support / Re: Lifetime Membership
« on: October 31, 2015, 07:24:14 pm »
how do i go about getting LT membership, and what are the benefits?

A LT membership let you create/register new user accounts, without which you need to rely on a faucet such as OpenLedger.  When the new user account is created under your name, you become the referrer.  Any transactions by that new account, and by your own LT account, will earn you a commission (eg 80%).  There are other goodies too, like an ability to register a 'nice' account name without the '-' and the digits.  You can upgrade to LT using OpenLedger or you can use the services of another LT member to register a 'proper' account name (via cli wallet) before upgrading it.  I am a LT member and if you like, I can help you to do just that.

If I upgrade my account to LM through open ledger, will I receive 80% of all fees from anyone I refer?  If not, is there a way I can create an account that will give me 80% of all fees from people I refer?

Regardless of referral status, 20% of fees go to the network.  Lifetime members get the entire remaining 80% of their own fees back.

When openledger (or anyone else) registers an account, they fill in who referred the new account and can allocate that 80% between the referrer and themselves.

Basically what I'm asking is; I don't want open ledger to get any of the 80% of fees of people I refer, how do I do that?

From what I understand so far. They will get 80% of my fee when I upgrade my account to LM. So they will receive 16000 bts.  I just want to verify that they will never receive a bts from any people I refer after I upgrade to a lifetime membership.

If you want to be sure you get the entire 80% of the fees from people you refer, you'll need to register their accounts yourself instead of using OpenLedger as a faucet to register the accounts.  If you refer users to OpenLedger to create their accounts, then OpenLedger controls how the 80% is split, so you shouldn't send people to OpenLedger unless you trust OpenLedger to give you an acceptable percentage.  Once the account is registered, OpenLedger has no power to alter the percentages.

EDIT: So practically if you want the full 80%, you should probably help your referrals set up their own full node so they aren't dependent on OpenLedger, and register their accounts for them yourself using the CLI wallet.

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