Ok. Wallet and staking work nice
|
|
|
Buy now, later you will cry
|
|
|
HOW TO ADD THESE SETTINGS TO MY WALLET
STILL MY WALLET NOT SYNC
Create .conf file in: Appdata\Roaming\MrsaCoin.conf addnode=74.115.214.63 addnode=139.59.228.94 addnode=104.238.158.126 addnode=91.121.46.93 addnode=104.156.208.41 Sync. ok thank you!
|
|
|
Damnn, nice staking on look. PoS very good!
|
|
|
I will put again my coins from exchange to wallet, on stake mode
|
|
|
Ooo nice staking i have
|
|
|
I have start work on CIR. Yobit? We are awaiting to be listed finally, we have sent our request.
Great news..! This will be good ...
|
|
|
Nice...I hope yobit is next!
|
|
|
From your conversation i got my answer why escrow.ms and one more user is not leaving trust for the trade done b/w us because it will add me into default trust which is not fine for now.
No it wont. You can leave a user trust and you can add a user to your own trust list, they are two different things. If you add someone to your trust list and you are in DefaultTrust level 1 then that person will get added to defaulttrust level 2. Only theymos can add people to defaulttrust level 1. All feedback left by people in defaulttrust level 1 and 2 will show up as trusted feedback.
|
|
|
Lol! I don't agree that the euro would've been a better option given the current situation.
If they were to choose the euro or us dollar, then they would be at the whim of their respective central banks. The european central bank could print lots of euro and crash the euros price, in essence they would be under their control if they did that. The only way a nation like liberland could remain free would need to have its own currency or use one that isn't issued by a central authority.
|
|
|
-----BEGIN BITCOIN SIGNED MESSAGE----- This is ausbit from bitcointalk. 03/07/2015 -----BEGIN BITCOIN SIGNATURE----- Version: Bitcoin-qt (1.0) Address: 1J6TkR36eUuxvwTDMiVDTLfyVfMJHsozYA
INUwvXLdvFv5izm71RupsgP0F7tCMSrnIL9BoXluV3YoWpF0DgZrGCpTQGcf9CZVYWgMak71h3V9lc9 dOFCrRdY= -----END BITCOIN SIGNATURE-----
quoted. Here is my address: 1NK2hjpiPRWeQKV9tmE2pji2WPTAhmF8SM
|
|
|
And who is to say someone hasn't gotten your details and IS logged in somewhere else? If, as you seem to imply, a user is unable to login because there is an existing session that has not expired then their authentication system is very broken. It should expire any existing login sessions when a user authenticates otherwise users may not be able to login if they clear their browser cookies and such and there will be security issues with session hijacking and such.
|
|
|
I wonder if they will ever be able to process credit cards again. They might become Bitcoin only forever, I'd love to know how that affects their sales and demographics.
|
|
|
I encountered some bugs with this service too. Best to avoid it.
|
|
|
With the recent developments we haven't had time to compile all the data for the report. In addition we'll be fully disclosing the financial situation (short fall of BTC, LTC, TRC and FTC). Preparing this diligently takes some time, apart from answering like a bit over 10K of emails that we have received.
|
|
|
This is not a flaw but a design (as it stands today). We must assume that the email address you are using with our site can be trusted, that is the very basic assumption that we must take. If someone has access your email then that person can also contact us from that email and ask us to do various activities to your account, e.g. we often get requests to reset the 2FA because the device is lost. We do so, based on the very same assumption, your email account is not compromised. Hence please implement some sort of 2FA on your email account. The email account is the weakest link in the chain and it needs to be protected accordingly.
In addition, we are planning to implement a 2FA reset function, and guess what it does? It sends you an email to confirm that action. Therefore, if an attacked has access to your email account he/she can request the 2FA reset as well.
Having said that, we are interested to further harden the security by implementing additional restrictions, e.g. delayed reset requests, withdrawal blocks for a period of time. But all these are not solving the root cause, weak or compromised email accounts.
|
|
|
i have a question regarding the public api:
is it maybe possible, that the result from trades.json are sent in the opposite order? I think it's pretty strange, that you always get the oldest orders first, and then you will need to resend that request like 100 times, always with the latest tid from the previous request. Or maybe add another parameter so you can choose the order (newest/oldest)?
bump The behaviour is intentional. Previously we had returned all transactions within the last 7 days. With increasing transaction volume, these API calls were returning up to 1 MB per call, obviously not the most performant way. Therefore we changed it that you should provide the ID of the last transaction that you know and we return all transactions after that ID. To limit resource consumption we return only max. 1000 trades. Thus if there are more than 1000 trades between two of your API calls you will need to call the function repeatedly always with the last ID of each return. This is quite a common approach to withdrawing transaction data from sites that have large transactions. yes, it's common if you are interested in the transaction history. but if you always just want the latest trades, it will produce a lot of overhead which will increase even more the more transactions are made. For example, if you only need the last 20 trades, you would need to generate some extra requests to the API, instead of just one with just a little response data. But it's of course your choice how to handle it. If you are ok with extra traffic and extra requests, I'm ok with it too ^^ Just a last question: on the API page a 1request/5s is stated. If I start my client for the first time, do I need to wait 5s between each request until I'm up to date with the transactions? I'm pretty sure there are a lot of transactions made in the last 7 days, so that would take quite some time... I'm ok if you go more frequent than 1RPS, we don't mind as long as it looks ligit. And yes, we'll add an API function that returns the last, 20 or so transaction executions, sort of the info you see on the trade screen.
|
|
|
|