Author

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 622. (Read 4670673 times)

legendary
Activity: 1008
Merit: 1001

Hey thanks for following up with them on that! We're happy to help any exchanges/services/etc. with integration as needed. IRC is usually the most efficient way.



You are welcome. I added the following to the ticket, if you provide me the IRC channel with the #, i'll be happy to forward it ->
Code:
 Sender: elrippos3/25/2016 8:26:56 AM


                        Dear Support,
your admins might want to check the [1] DevGuides on https://getmonero.org
If you face severe problems, you can always contact the devs at [email protected]

[1] https://getmonero.org/knowledge-base/developer-guides/

Kind regards,
elrippos.

Ps.: Polo Volume above 3K BTC
                   
legendary
Activity: 2968
Merit: 1198

Hey thanks for following up with them on that! We're happy to help any exchanges/services/etc. with integration as needed. IRC is usually the most efficient way.

legendary
Activity: 1008
Merit: 1001
If you remeber, i urged the community to vote for [XMR] on https://www.cryptopia.co.nz
We won the voting and we where told, that [XMR] will be handed with priority on October 2015, see my support ticket and the answer ->
Code:
#4046 - [XMR] Monero
Category: Exchange
Status: Closed
Opened: 10/14/2015 6:47:48 PM
Last Update: 10/17/2015 1:08:03 AM
Ticket description:

Dear support,
would you be so kind to give me an estimate when XMR Monero will appear in the exchange?

Kind regards,
elrippos
Code:
    Sender: sa_ddam21310/14/2015 10:19:55 PM


                            Hi,

    Unfortunately we don't have an estimate at this time as we need to make several changes to our platform to support Monero. and other CryptoNote coins.

    However we are working on this as a priority :)



    Thanks               

It's been a while and yesterday i asked about the implementation of [XMR] and got an answer ->
Code:
#5506 - [XMR] Monero Trading
Category: Exchange
Status: Closed
Opened: 3/23/2016 11:01:31 AM
Last Update: 3/24/2016 1:11:41 AM
Ticket description:

Dear support,

would you be so kind to tell me when you will start deploying [XMR] Monero for Exchange and Trading.
My last asking was in October 2015 and you stated you are working on priority.

I hope you did not miss the trading volume on Poloniex for Monero, at the average above 1K BTC daily.
I may urge you to deploy Monero as fast as you can with release 0.9.3

Kind regards,
elrippos
Code:
    Sender: sa_ddam2133/24/2016 1:11:18 AM


                            Hi,

    XMR is currently still being tested in our backend, there are still a few issues with the wallet using excessive amounts of memory and random crashes we are trying to resolve, this has required us to build a monitoring service for XMR which has extended the time to get this coin integrated.

    Once these last few problems are resolved XMR will be enabled on the site.



    Thnaks
                       

Since he stated of massive RAM usage i urged the usage of the 0.9.x binaries today, answer will be posted as soon as they respond ->
Code:
#5519 - [XMR] Monero implementation with DB support instead of RAM usage
Category: Exchange
Status: New
Opened: 3/24/2016 9:17:23 AM
Last Update: 3/24/2016 9:17:23 AM
Ticket description:

Dear Support,

if you want to implement [XMR] quickly, you should install the latest [1] [2] 0.9.x binaries with DB support, instead of using oldish binaries with massive RAM usage.
You can also use [3] instructions for your platform to make your live easier.

I urge you to implemet Monero for your prosperous business.

Help can be found on the [4] official HP with DEV support.

[1] https://getmonero.org/downloads/
[2] https://github.com/monero-project/bitmonero
[3] https://moneroxzfonkazxc.torstorm.org/
[4] https://getmonero.org/

If i can assist you, get back to me!

Kind regards,
elrippos
Code:
    Sender: MrFloppy3/24/2016 6:22:53 PM


                            Hi, i've pass this onto the admins for their consideration, and they will get back to you.
    have a nice day -Cryptopia Team
                       
legendary
Activity: 2968
Merit: 1198
what services are coming, or features to monero that may increase its usage? the value seems stagnant for long time already

Please stop sigspamming.

it was a legit question but since you think it was spam, i'll post this again in one week without the sig, i'm curious about your answer

Your 'legit' question makes no sense when the 'stagnant' value has increased 300% in a few months and has regular daily double digit swings.

So I'm giving you the benefit of the doubt that you are sigspamming and not merely stupid. Please go away.

In case anyone else is interested, here are the design and development goals: http://getmonero.org/design-goals/
legendary
Activity: 2590
Merit: 1022
Leading Crypto Sports Betting & Casino Platform
what services are coming, or features to monero that may increase its usage? the value seems stagnant for long time already

Please stop sigspamming.

it was a legit question but since you think it was spam, i'll post this again in one week without the sig, i'm curious about your answer
legendary
Activity: 2968
Merit: 1198
Concerning sweep_dust - I transfered those coins to another wallet but had to split in many transactions and most of the 1 XMR said being dust transfered. But total fee was quite big ~ around 5 XMR fee for sending 280 XMR. There were a lot of tiny inputs that's the reason.

Today I caught another interesting error. After PC crash (I guess electricity surge) daemon refused to start:

Code:
2016-Mar-25 08:59:38.650014 Initializing core...
2016-Mar-25 08:59:38.652014 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...
2016-Mar-25 08:59:38.653514 option: fastest
2016-Mar-25 08:59:38.654514 option: async
2016-Mar-25 08:59:38.655014 option: 1000
2016-Mar-25 08:59:38.698525 Error attempting to retrieve a hard fork version at height 1010595 from the db: MDB_NOTFOUND: No matching key/data pair found
2016-Mar-25 08:59:38.700025 ERROR C:/msys64/DISTRIBUTION-BUILD/src/daemon/daemon.cpp:144 Uncaught exception! Error attempting to retrieve a hard fork version at height 1010595 from the db: MDB_NOTFOUND: No matching key/data pair found
2016-Mar-25 08:59:38.702526 Deinitializing rpc server...
2016-Mar-25 08:59:38.703026 Deinitializing p2p...
2016-Mar-25 08:59:38.707527 Deinitializing core...
2016-Mar-25 08:59:38.709528 Closing IO Service.
2016-Mar-25 08:59:38.741036 Deinitializing cryptonote_protocol...

I restored and synced from backup made day earlier and now it works. Maybe this info will be somehow useful to the devs.

That is a known issue and is being worked on. Thanks for reporting!
legendary
Activity: 1750
Merit: 1101
karbo.io
Concerning sweep_dust - I transfered those coins to another wallet but had to split in many transactions and most of the 1 XMR said being dust transfered. But total fee was quite big ~ around 5 XMR fee for sending 280 XMR. There were a lot of tiny inputs that's the reason.

Today I caught another interesting error. After PC crash (I guess electricity surge) daemon refused to start:

Code:
2016-Mar-25 08:59:38.650014 Initializing core...
2016-Mar-25 08:59:38.652014 Loading blockchain from folder C:\ProgramData\bitmonero\lmdb ...
2016-Mar-25 08:59:38.653514 option: fastest
2016-Mar-25 08:59:38.654514 option: async
2016-Mar-25 08:59:38.655014 option: 1000
2016-Mar-25 08:59:38.698525 Error attempting to retrieve a hard fork version at height 1010595 from the db: MDB_NOTFOUND: No matching key/data pair found
2016-Mar-25 08:59:38.700025 ERROR C:/msys64/DISTRIBUTION-BUILD/src/daemon/daemon.cpp:144 Uncaught exception! Error attempting to retrieve a hard fork version at height 1010595 from the db: MDB_NOTFOUND: No matching key/data pair found
2016-Mar-25 08:59:38.702526 Deinitializing rpc server...
2016-Mar-25 08:59:38.703026 Deinitializing p2p...
2016-Mar-25 08:59:38.707527 Deinitializing core...
2016-Mar-25 08:59:38.709528 Closing IO Service.
2016-Mar-25 08:59:38.741036 Deinitializing cryptonote_protocol...

I restored and synced from backup made day earlier and now it works. Maybe this info will be somehow useful to the devs.
legendary
Activity: 2968
Merit: 1198
on my wallet i tried sweep_dust and transfer 100xmr all failed.

There is a known issue with sweep_dust sometimes not working. That is being addressed in a future update.

As far as the other, we're taking a look at your log file, but GingerAle's suggestion about going on IRC is a good one. Sometimes it is best to be able to ask questions and try things in real time.


legendary
Activity: 1260
Merit: 1008
status
Height: 1010798/1010798 (100.0%) on mainnet, not mining, net hash 11.97 MH/s, v2, up to date, 5+22 connections
2016-Mar-25 10:09:10.190833 [P2P2][80.251.137.218:34728 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 10:09:16.911951 [P2P2][212.36.13.6:64954 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
    i have synced with the network, but there must be something wrong.
    when i transfer my coins got this error
    Error: transaction <365b9fc57722ce1b5cf5bbbc0a43a58995513d7adcf054ddc5da00115fa27b1a> was rejected by daemon with status: Failed
    2016-Mar-25 10:11:15.687045 [RPC1][on_send_raw_tx]: Failed to process tx

What is shown in your bitmonerod.log file?


Lorgs


join #monero on IRC

https://kiwiirc.com/client

pick a nickname and enter #monero in the channel box.
full member
Activity: 173
Merit: 100
status
Height: 1010798/1010798 (100.0%) on mainnet, not mining, net hash 11.97 MH/s, v2, up to date, 5+22 connections
2016-Mar-25 10:09:10.190833 [P2P2][80.251.137.218:34728 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 10:09:16.911951 [P2P2][212.36.13.6:64954 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
    i have synced with the network, but there must be something wrong.
    when i transfer my coins got this error
    Error: transaction <365b9fc57722ce1b5cf5bbbc0a43a58995513d7adcf054ddc5da00115fa27b1a> was rejected by daemon with status: Failed
    2016-Mar-25 10:11:15.687045 [RPC1][on_send_raw_tx]: Failed to process tx

What is shown in your bitmonerod.log file?
set_log 1   {p1} 2016-03-25 11:20:22.937952 [connection_basic.cpp+174 ::~connection_basic] Destructing connection p2p#31
2016-Mar-25 11:20:23.997601 Read command: set_log 1
Log level is now 1
2016-Mar-25 11:20:33.908410 [P2P5]transaction with hash ac352235b96894aa9f294521fe7d5eb74742a5090c4b6d67145979b42c14e7c7 not found in db
2016-Mar-25 11:20:33.949939 [P2P5]t_loop: 0
2016-Mar-25 11:20:33.950439 [P2P5]tx added:
2016-Mar-25 11:20:41.051429 [P2P7]+++++ BLOCK SUCCESSFULLY ADDED
id:     <1ffbf835f7f1fbe292186bff6c1861c92a03d3c1f1a3e997219e5526874e055f>
PoW:   
HEIGHT 1010829, difficulty:     1413055120
block reward: 13.441000000000(13.441000000000 + 0.000000000000), coinbase_blob_size: 249, cumulative size: 249, 32(0/32)ms
2016-Mar-25 11:20:47.600151 [P2P9][188.191.97.234:18080 OUT]Got NEW BLOCKS inside of handle_response_get_objects: size: 107
2016-Mar-25 11:20:47.601130 [P2P9]block_batches: 26
2016-Mar-25 11:20:47.601130 [P2P9]Skipping prepare blocks. New blocks don't belong to chain.
2016-Mar-25 11:20:47.634369 [P2P9]Block with id:
 for alternative chain, does not have enough proof of work: <86bf25bfe650343ac77c048d722fa09cefb848287d0aaec934fbb32304000000>
 expected difficulty: 1602577457
2016-Mar-25 11:20:47.634369 [P2P9][188.191.97.234:18080 OUT]Block verification failed, dropping connection
2016-Mar-25 11:20:47.636323 [P2P9]IP 188.191.97.234 fail score=1
2016-Mar-25 11:20:48.861275 [P2P6]Connecting to 176.240.53.98:18080(white=0, last_seen: d0.h6.m4.s7)...
2016-Mar-25 11:20:50.866119 [P2P6][0.0.0.0:0 OUT]Connect failed to 176.240.53.98:18080
2016-Mar-25 11:20:50.867097 [P2P6]Connecting to 111.174.204.217:18080(white=0, last_seen: d0.h0.m14.s29)...
MARK   {7} {p1} 2016-03-25 11:20:50.895448 [abstract_tcp_server2.inl+259 ::save_dbg_log]  connection type P2P 192.168.4.106:50174 <--> 111.174.204.217:18080

2016-Mar-25 11:20:54.532263 [RPC0]transaction with hash 29be3bf532bccfc86147844b3bb91efa2a78b81e30606aa7a50d462e85a127f5 not found in db
2016-Mar-25 11:20:54.533242 [RPC0]transaction fee is not enough: 0.670000000000, minimum fee: 0.680000000000
2016-Mar-25 11:20:54.534219 [RPC0]Transaction verification failed: <29be3bf532bccfc86147844b3bb91efa2a78b81e30606aa7a50d462e85a127f5>
2016-Mar-25 11:20:54.536175 [RPC0][on_send_raw_tx]: Failed to process tx
2016-Mar-25 11:20:55.957922 [P2P9]Failed to invoke command 1001 return code -4
2016-Mar-25 11:20:55.957922 [P2P9][111.174.204.217:18080 OUT]COMMAND_HANDSHAKE invoke failed. (-4, LEVIN_ERROR_CONNECTION_TIMEDOUT)
2016-Mar-25 11:20:55.959877 [P2P6][111.174.204.217:18080 OUT]COMMAND_HANDSHAKE Failed
2016-Mar-25 11:20:55.960854 [P2P6][111.174.204.217:18080 OUT]Failed to HANDSHAKE with peer 111.174.204.217:18080
2016-Mar-25 11:21:06.183398 [P2P6]transaction with hash ac352235b96894aa9f294521fe7d5eb74742a5090c4b6d67145979b42c14e7c7 not found in db
2016-Mar-25 11:21:06.186331 [P2P6]t_loop: 0
2016-Mar-25 11:21:06.263564 [P2P6]+++++ BLOCK SUCCESSFULLY ADDED
id:     
PoW:    <566333cc75bc21ef09a129d782d96b0f481a18881ab1ad75297f7c1c00000000>
HEIGHT 1010830, difficulty:     1405325524
block reward: 13.541000000000(13.441000000000 + 0.100000000000), coinbase_blob_size: 249, cumulative size: 960, 31(0/31)ms
2016-Mar-25 11:21:07.215760 [P2P6]Failed to invoke command 1002 return code -4
2016-Mar-25 11:21:07.215760 [P2P6][190.19.174.65:18080 OUT]COMMAND_TIMED_SYNC invoke failed. (-4, LEVIN_ERROR_CONNECTION_TIMEDOUT)
2016-Mar-25 11:21:07.217716 [P2P6]Failed to invoke command 1002 return code -3
2016-Mar-25 11:21:07.218693 [P2P6][190.19.174.65:18080 OUT]COMMAND_TIMED_SYNC invoke failed. (-3, LEVIN_ERROR_CONNECTION_DESTROYED)
2016-Mar-25 11:21:07.376088 [P2P6]Failed to invoke command 1002 return code -3
2016-Mar-25 11:21:07.376088 [P2P6][106.187.42.214:18080 OUT]COMMAND_TIMED_SYNC invoke failed. (-3, LEVIN_ERROR_CONNECTION_DESTROYED)
2016-Mar-25 11:21:09.964847 [P2P6]Connecting to 185.21.218.131:18080(white=0, last_seen: d0.h0.m40.s14)...
2016-Mar-25 11:21:14.966457 [P2P6][0.0.0.0:0 OUT]Connect failed to 185.21.218.131:18080
2016-Mar-25 11:21:14.968395 [P2P6]Connecting to 191.205.62.6:18080(white=0, last_seen: d0.h2.m44.s35)...
2016-Mar-25 11:21:17.501394 [P2P6][0.0.0.0:0 OUT]Connect failed to 191.205.62.6:18080
2016-Mar-25 11:21:17.503350 [P2P6]Connecting to 71.71.107.254:18080(white=0, last_seen: d0.h6.m53.s16)...
2016-Mar-25 11:21:22.505690 [P2P6][0.0.0.0:0 OUT]Connect failed to 71.71.107.254:18080
2016-Mar-25 11:22:15.693636 [P2P4]+++++ BLOCK SUCCESSFULLY ADDED
id:     <0b40d07fd9ab390dc216296a060a640b0a2d4fb73e8056b98d11658a7c8062b2>
PoW:   
HEIGHT 1010831, difficulty:     1405451374
block reward: 13.441000000000(13.441000000000 + 0.000000000000), coinbase_blob_size: 249, cumulative size: 249, 63(0/63)ms
2016-Mar-25 11:22:48.720036 [P2P6]Connecting to 23.91.145.122:18080(white=0, last_seen: d0.h4.m27.s13)...
2016-Mar-25 11:22:50.639077 [P2P7]transaction with hash cf501be45aafe83116407c0214496d060e7d330c2db42d4fca3d35100153644e not found in db
2016-Mar-25 11:22:50.879954 [P2P7]t_loop: 0
2016-Mar-25 11:22:50.879954 [P2P7]tx added:
2016-Mar-25 11:22:53.722325 [P2P6][0.0.0.0:0 OUT]Connect failed to 23.91.145.122:18080
2016-Mar-25 11:22:53.722325 [P2P6]Connecting to 72.131.14.133:18080(white=0, last_seen: d0.h1.m34.s58)...
2016-Mar-25 11:22:55.994130 [P2P6][0.0.0.0:0 OUT]Connect failed to 72.131.14.133:18080
2016-Mar-25 11:22:55.994130 [P2P6]Connecting to 46.240.170.28:18080(white=0, last_seen: d0.h3.m40.s40)...
2016-Mar-25 11:23:00.996905 [P2P6][0.0.0.0:0 OUT]Connect failed to 46.240.170.28:18080
2016-Mar-25 11:23:00.996905 [P2P6]Connecting to 176.240.53.98:18080(white=0, last_seen: d0.h6.m6.s19)...
2016-Mar-25 11:23:03.314829 [P2P6][0.0.0.0:0 OUT]Connect failed to 176.240.53.98:18080
2016-Mar-25 11:23:03.314829 [P2P6]Connecting to 119.142.9.217:18080(white=0, last_seen: d0.h0.m30.s46)...
MARK   {7} {p1} 2016-03-25 11:23:03.361757 [abstract_tcp_server2.inl+259 ::save_dbg_log]  connection type P2P 192.168.4.106:50238 <--> 119.142.9.217:18080

2016-Mar-25 11:23:03.703921 [P2P8][119.142.9.217:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Mar-25 11:23:03.704899 [P2P6]Connecting to 90.8.243.210:18080(white=0, last_seen: d0.h5.m33.s44)...
2016-Mar-25 11:23:08.707073 [P2P6][0.0.0.0:0 OUT]Connect failed to 90.8.243.210:18080
2016-Mar-25 11:23:08.708048 [P2P6]Connecting to 86.171.16.197:18080(white=0, last_seen: d0.h6.m34.s39)...
2016-Mar-25 11:23:13.710444 [P2P6][0.0.0.0:0 OUT]Connect failed to 86.171.16.197:18080
2016-Mar-25 11:23:13.710944 [P2P6]Connecting to 111.174.204.217:18080(white=0, last_seen: d0.h0.m16.s52)...
MARK   {7} {p1} 2016-03-25 11:23:13.738463 [abstract_tcp_server2.inl+259 ::save_dbg_log]  connection type P2P 192.168.4.106:50246 <--> 111.174.204.217:18080

2016-Mar-25 11:23:14.059994 [P2P8][111.174.204.217:18080 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Mar-25 11:23:14.060954 [P2P6]Connecting to 191.205.62.6:18080(white=0, last_seen: d0.h2.m46.s35)...
2016-Mar-25 11:23:19.061984 [P2P6][0.0.0.0:0 OUT]Connect failed to 191.205.62.6:18080
2016-Mar-25 11:23:19.061984 [P2P6]Connecting to 93.120.194.114:18080(white=0, last_seen: d0.h7.m11.s19)...
2016-Mar-25 11:23:22.056896 [P2P7]transaction with hash ba7ae3fbe2fb4ef2ecb3ee96e3eeaa4cdb5d4bfd2dd810247ab8e45489b31e82 not found in db
2016-Mar-25 11:23:22.114435 [P2P7]t_loop: 0
2016-Mar-25 11:23:22.115438 [P2P7]tx added:
2016-Mar-25 11:23:24.064647 [P2P6][0.0.0.0:0 OUT]Connect failed to 93.120.194.114:18080
2016-Mar-25 11:23:24.064647 [P2P6]Connecting to 176.240.53.98:18080(white=0, last_seen: d0.h6.m6.s43)...
2016-Mar-25 11:23:26.130117 [P2P6][0.0.0.0:0 OUT]Connect failed to 176.240.53.98:18080
2016-Mar-25 11:23:26.131076 [P2P6]Connecting to 90.8.243.210:18080(white=0, last_seen: d0.h5.m34.s7)...
2016-Mar-25 11:23:31.133130 [P2P6][0.0.0.0:0 OUT]Connect failed to 90.8.243.210:18080
2016-Mar-25 11:23:31.133130 [P2P6]Connecting to 109.63.166.55:18080(white=0, last_seen: d0.h0.m2.s6)...
MARK   {7} {p1} 2016-03-25 11:23:34.784157 [abstract_tcp_server2.inl+259 ::save_dbg_log]  connection type P2P 192.168.4.106:50255 <--> 109.63.166.55:18080

2016-Mar-25 11:23:39.911415 [P2P8]Failed to invoke command 1001 return code -4
2016-Mar-25 11:23:39.911915 [P2P8][109.63.166.55:18080 OUT]COMMAND_HANDSHAKE invoke failed. (-4, LEVIN_ERROR_CONNECTION_TIMEDOUT)
2016-Mar-25 11:23:39.913416 [P2P6][109.63.166.55:18080 OUT]COMMAND_HANDSHAKE Failed
2016-Mar-25 11:23:39.915417 [P2P6][109.63.166.55:18080 OUT]Failed to HANDSHAKE with peer 109.63.166.55:18080
2016-Mar-25 11:23:42.646199 [RPC0]transaction with hash 849c54a5e61cbf84da46c0913b4ea2ffabae8ce5994a1ffb496f60860609ef10 not found in db
2016-Mar-25 11:23:42.665752 [RPC0]Tx <849c54a5e61cbf84da46c0913b4ea2ffabae8ce5994a1ffb496f60860609ef10> has too low mixin (0), and more than one mixable input with unmixable inputs
2016-Mar-25 11:23:42.667708 [RPC0]tx used wrong inputs, rejected
2016-Mar-25 11:23:42.668685 [RPC0]Transaction verification failed: <849c54a5e61cbf84da46c0913b4ea2ffabae8ce5994a1ffb496f60860609ef10>
2016-Mar-25 11:23:42.670639 [RPC0][on_send_raw_tx]: Failed to process tx



i did't found bitmonerod.log with 0.9.3.0,i set_log 1
on my wallet i tried sweep_dust and transfer 100xmr all failed.
legendary
Activity: 2968
Merit: 1198
status
Height: 1010798/1010798 (100.0%) on mainnet, not mining, net hash 11.97 MH/s, v2, up to date, 5+22 connections
2016-Mar-25 10:09:10.190833 [P2P2][80.251.137.218:34728 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 10:09:16.911951 [P2P2][212.36.13.6:64954 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
    i have synced with the network, but there must be something wrong.
    when i transfer my coins got this error
    Error: transaction <365b9fc57722ce1b5cf5bbbc0a43a58995513d7adcf054ddc5da00115fa27b1a> was rejected by daemon with status: Failed
    2016-Mar-25 10:11:15.687045 [RPC1][on_send_raw_tx]: Failed to process tx

What is shown in your bitmonerod.log file?
full member
Activity: 173
Merit: 100
status
Height: 1010798/1010798 (100.0%) on mainnet, not mining, net hash 11.97 MH/s, v2, up to date, 5+22 connections
2016-Mar-25 10:09:10.190833 [P2P2][80.251.137.218:34728 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
2016-Mar-25 10:09:16.911951 [P2P2][212.36.13.6:64954 INC]Sync data returned unknown top block: 1010798 -> 1009932 [866 blocks (0 days) ahead]
SYNCHRONIZATION started
    i have synced with the network, but there must be something wrong.
    when i transfer my coins got this error
    Error: transaction <365b9fc57722ce1b5cf5bbbc0a43a58995513d7adcf054ddc5da00115fa27b1a> was rejected by daemon with status: Failed
    2016-Mar-25 10:11:15.687045 [RPC1][on_send_raw_tx]: Failed to process tx
legendary
Activity: 2016
Merit: 1259
legendary
Activity: 952
Merit: 1000
Stagnation is Death
Whats the emission now guys
legendary
Activity: 2268
Merit: 1141
legendary
Activity: 1610
Merit: 1004
monero-nodejs 3.0 update
https://github.com/PsychicCat/monero-nodejs

I recently updated the monero-nodejs library for simplewallet. Changes:
  • Refactored to use zero dependencies. Never worry about breaking changes in the future, and it should be compatible with most environments.
  • Tests! Clone the repository and run npm install && npm test to test if your wallet is configured properly.
legendary
Activity: 1260
Merit: 1008
I'm wondering why block time was increased, where can I read about it?

There is a thread with the proposal and discussion:

https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time

Yes! Thank you Dr. Bookmarks.

And btw the new american pegasus inspired yacht moon thing with all the peeps on it is.... amazing.
full member
Activity: 308
Merit: 109
Will MyMonero.com be up on tomorrow 25. March 06.00 GMT?
legendary
Activity: 2268
Merit: 1141
I'm wondering why block time was increased, where can I read about it?

There is a thread with the proposal and discussion:

https://forum.getmonero.org/20/general-discussion/2401/increasing-the-block-time
Jump to: