Main Menu

Poloniex Deposit

Started by bitacer, February 15, 2016, 06:52:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jambo110

still waiting on my withdrawal  Being Processed since 1 days 15 hours

clayop

The real problem is polo mods and supports don't realize this issue for 24 hours. If this happens again, run to polo trollbox and complain about it (after creating a ticket)
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

liondani

opened a ticket on poloniex for a withdrawal of 102000 BTS yesterday that still don't show up...
will inform further
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

abit

Quote from: xeroc on February 24, 2016, 12:50:33 PM
Quote from: abit on February 24, 2016, 12:14:00 PM
Quote from: xeroc on February 17, 2016, 07:38:05 AM
Quote from: testz on February 17, 2016, 07:03:06 AM
Quote from: clayop on February 17, 2016, 05:50:56 AM
I'm having this problem again.

And FYI, they missed some deposited because of broken "get_account_history" API. I sent them a simple script to detect them.

If it's can be fixed, please open the issue at github: https://github.com/cryptonomex/graphene/issues
Afaik that issue jas been fixed withblatest release
The one get fixed is another issue. I think it's not high priority and few people using cli_wallet or that API and many people (for example roadscape) already know that, so didn't bother open an issue.

@xeroc you can simply try these commands in cli_wallet to see if it's buggy:

get_account_history in.abit 100
get_account_history in.abit 101


works for me

Here are the results:

get_account_history in.abit 100
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
...
2016-02-24T16:57:33 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T16:08:48 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T16:08:48 asset_publish_feed_operation in.abit fee: 0.10000 BTS


get_account_history in.abit 101
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T20:38:30 asset_publish_feed_operation in.abit fee: 0.10000 BTS
...
2016-02-24T16:57:33 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T16:08:48 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-24T16:08:48 asset_publish_feed_operation in.abit fee: 0.10000 BTS
2016-02-21T14:39:06 asset_publish_feed_operation in.abit fee: 0.10000 BTS

Apprarently the 101 one is missing a lot of records. My witness publishes price feeds EVERYDAY. But where are the records between 2016-02-21T14:39:06 and 2016-02-24T16:08:48?
BitShares committee member: abit
BitShares witness: in.abit

clayop

Quote from: xeroc on February 24, 2016, 12:50:33 PM
Quote from: abit on February 24, 2016, 12:14:00 PM
Quote from: xeroc on February 17, 2016, 07:38:05 AM
Quote from: testz on February 17, 2016, 07:03:06 AM
Quote from: clayop on February 17, 2016, 05:50:56 AM
I'm having this problem again.

And FYI, they missed some deposited because of broken "get_account_history" API. I sent them a simple script to detect them.

If it's can be fixed, please open the issue at github: https://github.com/cryptonomex/graphene/issues
Afaik that issue jas been fixed withblatest release
The one get fixed is another issue. I think it's not high priority and few people using cli_wallet or that API and many people (for example roadscape) already know that, so didn't bother open an issue.

@xeroc you can simply try these commands in cli_wallet to see if it's buggy:

get_account_history in.abit 100
get_account_history in.abit 101


works for me
If there's a lot of txs it misses some txs.
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

BitShares News

Quote from: aloha on February 24, 2016, 02:59:35 PM
Quote from: cylonmaker2053 on February 24, 2016, 01:59:07 PM
Has anyone else figured out a good spot to park ETH other than Poloniex? I would like to diversify out of the exchange a bit.
I am using Kryptokit Ethereum Wallet in beta. So far no problems, very simple works well.

I like Mist.
This blog has ceased operation. [url="http://goo.gl/2uU8s7"]http://goo.gl/2uU8s7[/url]

monsterer

Quote from: cylonmaker2053 on February 24, 2016, 01:59:07 PM
Has anyone else figured out a good spot to park ETH other than Poloniex? I would like to diversify out of the exchange a bit.

Trade ETH on bitshares if you like: https://metaexchange.info/markets/METAEX.ETH/ETH
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

vegolino

Quote from: cylonmaker2053 on February 24, 2016, 01:59:07 PM
Has anyone else figured out a good spot to park ETH other than Poloniex? I would like to diversify out of the exchange a bit.
I am using Kryptokit Ethereum Wallet in beta. So far no problems, very simple works well.

xeroc

Kraken.com also trades ETH ..
and I think metaexchange has an IOU for ETH on BitShares as well ..

cylonmaker2053

Has anyone else figured out a good spot to park ETH other than Poloniex? I would like to diversify out of the exchange a bit.

xeroc

Quote from: abit on February 24, 2016, 12:14:00 PM
Quote from: xeroc on February 17, 2016, 07:38:05 AM
Quote from: testz on February 17, 2016, 07:03:06 AM
Quote from: clayop on February 17, 2016, 05:50:56 AM
I'm having this problem again.

And FYI, they missed some deposited because of broken "get_account_history" API. I sent them a simple script to detect them.

If it's can be fixed, please open the issue at github: https://github.com/cryptonomex/graphene/issues
Afaik that issue jas been fixed withblatest release
The one get fixed is another issue. I think it's not high priority and few people using cli_wallet or that API and many people (for example roadscape) already know that, so didn't bother open an issue.

@xeroc you can simply try these commands in cli_wallet to see if it's buggy:

get_account_history in.abit 100
get_account_history in.abit 101


works for me

abit

Quote from: xeroc on February 17, 2016, 07:38:05 AM
Quote from: testz on February 17, 2016, 07:03:06 AM
Quote from: clayop on February 17, 2016, 05:50:56 AM
I'm having this problem again.

And FYI, they missed some deposited because of broken "get_account_history" API. I sent them a simple script to detect them.

If it's can be fixed, please open the issue at github: https://github.com/cryptonomex/graphene/issues
Afaik that issue jas been fixed withblatest release
The one get fixed is another issue. I think it's not high priority and few people using cli_wallet or that API and many people (for example roadscape) already know that, so didn't bother open an issue.

@xeroc you can simply try these commands in cli_wallet to see if it's buggy:

get_account_history in.abit 100
get_account_history in.abit 101

BitShares committee member: abit
BitShares witness: in.abit

clayop

Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

cylonmaker2053


clayop

Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop