I decided not to dip into my cold storage just to mess around testing this, LOL...

So, just quickly bought five bucks worth on Polo and I'm now sending to this new address as TEST.

First "glitch" :: the Payment ID generated by the GUI wallet was not accepted by Poloniex SEND page... said "invalid" for some reason.

It's very short: 74f2ee14a7cb8dc8 in this case.  Not what I'm used to seeing, is this something new Polo needs to update for, or something is wrong?

Anyway, sending with no ID worked... transaction is still 'pending' on Polo and has not hit the GUI wallet yet so I'll update here after it comes thru.

{Edit} Update: That was quick!!  It just went out from Polo and already popped up on the GUI screen! 

Checking same address/seed in MyMonero shows NOTHING yet (as usual, I've noticed in the past that MM tends to take quite a long time to show correct balance and transaction info...)

SO... so far so good.  Amount I sent is not "unlocked" yet but I expect that's just a few confirmations?  Will check it after dinner and then try SENDING

Jaquee - Just a quick note to thank you for all the work you've done on the GUI. If you're ever around Boston I'll buy you a beer or three.

+1 Thanks Jaquee (and all the other hard working devs   )

FWIW, I have not tried GUI beta yet, but I DL'd and installed the Daemon (Wolfram Warptangent) on W10 (don't hate me for that please  ) at the weekend. Worked faultlessly. Took about 10 hours to DL and sync blockchain on an Ultrabook with i5 Core, SSD and 4GB RAM. Blockchain is about 8GB. The longest part seemed to be the last few months of the blockchain. Seemed like there were more peers syncing from me and less peers with newer blocks available. I guess that is to be expected ??

Now that it's up to date, running as node takes up very little CPU overhead for those that are wondering, and is something I am very happy to do whenever it's switched on (>12 hours a day usually). It is not noticeable running in the background, no noticeable performance effect.

One thing to note was that my total usage was >100GB for the 'sync day', presumably as I was both syncing and others were syncing from me at same time. Not sthg I can do every day, so adjusted the limits in the daemon to levels I can cover (easily done). I guess that could be done on initial sync day, but might slow things down ??

The new wallet worked fine too once I figured out CLI (not hard). Really like the feature that you can choose the block to start refreshing from. On my not-so-great machine, it takes about 10 mins per 2 months of blocks when restoring using mnemonic seed. Did a few tx's on some new test wallets, all good, very easy.

Hoping this info might encourage more people who have not done so yet to attempt the process and fire up a node ... full GUI will be gr8, but what we already have is solid anyway  

Thanks again dev team, and apologies if this is not the right place for this post. Just wanted to share

For SSD this sounds way to much.  You were using computer for something else then syncing? Maybe syncing Bitcoin wallet also?

Thanks for your kind words. Seems like i have a lot of beers to collect!

I've added a Windows build here if more people would like to test
https://github.com/Jaqueeee/monero-core/releases/tag/pre-beta

the remote daemon you are connected to has the wrong version

Is no one interested in the price shenanigans?!

I know it's Thanksgiving and all that, but not all of us are Yanks ;-)

Whatever happened to 'speculation'?

XMR is showing some reversed head and shoulder pattern on the 1-day and 4-h chart, this could be a nice bullish breakout.

Looks great! But honestly, I'm used to the CLI wallet.
I hope CLI wallet will still be available after the GUI has been released.