In my opinion, shitcoin is no volume, useless and no one want to hold it.

Lol i did not trust NEO again

I am still holding NEO. I hold NEO from 20$ up to now and my funds was decreased more than 50% of neo

Hi, if you are a long term holder, This is the time for buy, holding long-time will bring big profit. If you are a trader, please look at the market every day and make the decision.

I did a 32-bit build of the Windows wallet and uploaded the link to the 1st post.  Enjoy

Hey guys, development and work on the XAI project still continues on.  There is a lot of work to do and limited resources, but it has not stopped.  My time horizon on this is long term, but it won't be abandoned.

A couple of things I've got cooking:

- Implementing the new wallet design from our designer
- Solution for the scripting shell that cross-compiles on all platforms
- I was contacted by a guy from SuperNET and responded
- I am working with an advisor who has also advised some other notable projects on bolstering our presence in the Asian market

I have also been looking at a cool board I found:

https://www.parallella.org/

These boards are affordable and similar to a raspi, but have a multicore risc processor on board.  Down the road this could be a pretty cool hardware device for XAI so people can get an off the shelf computing "neurominer".  I'm hoping to get my hands on one of these boards soon.

Hey there, XQN is not abandoned   I'll put some updates together.

We have had a number of resources out there, but it seems that the only Quotient stuff that comes my way are occasional skype messages about it, but not much in the way of community activity around the coin.  The code base is solid, it has some great features, and is IMHO (although I know I built it so I'm biased) one of the better looking wallets out there.  It would be nice to see the community get involved too and build some cool stuff, like services or games or....well whatever people want.

XQN is also, if you guys haven't realized, one of the stronger coin networks out there.  Like there are hundreds of active wallets alive on the network staking.  I know this, because I just noticed that the seed node has used over 3x its bandwidth allotment at my provider and I'm getting hit with overage fees   Considering the state of the crypto scene lately, I find this kind of impressive.

Somebody asked me in a PM for a rich list, so I'm going to swap our block explorer over to a different one that I discovered that has a rich list function built in.

I'm working on the underlying wallet tech that will enable building this, then we have to implement the new UX design.

This from the guy who is attempting to pump...wait for it... BitBeans.   

We've updated our ANN post with our rebranded logo, infographics, and graphical elements.

Special thanks to crz for the amazing rebranding and wallet mockups.  Donations directly to crz may be sent to: AZKSvu5C3WP8awmLG2s1oqVZQdfnEF5Ve3

Our redesigned wallet UI courtesy of crz:

I pushed an update to github and tagged the last public version and the latest commit (6.1.14 and 6.2.21).  I'm still beating my head against the wall trying to get the Windows build to work, I had a workaround that I thought would work but it just results in strange undefined reference issues - which was to embed libqtlua within the source tree and build it that way.  But libqtlua is using headers with inline declarations and my suspicion is that mingw can't handle the mixing and matching like that.  I thought I had it working but when I did a make clean and tried to build from scratch it started spewing those issues again.  To build it on Linux you need Lua 5.3 and libqtlua 2.0, on my system I put them in ~/deps/lua and ~/deps/libqtlua, if you put them somewhere else you'll want to update the paths in the .pro file.  Works like a charm on Linux.

So what you'll see is that for IBTP the simple way I am doing the integration across coin networks is by filtering on the pchMessageStart.  I pre-load a directory of known chains:


And then in ProcessMessage all of the various message handling gets a check on a flag set on the node object:


When the node first connects and does the version handshake, it detects if it is not an XAI note and in the IBTP directory and sets the fForeignNode flag.  And thats it, from then on you can differentiate between native or non-native blockchains and handle the messaging appropriately.

Exactly.  The point of open sourcing it is so folks can compile it for various platforms, linux raspberry pi etc. and play around with it.  It's too much of a pain trying to maintain a public vs. closed version and two codebases.  I'm working on solving another linker issue then I'll push the code.

:shrug: If you want to sell then sell, there have been plenty of opportunities to exit.  The crypto landscape and alts in particular have dried up in terms of volume and viable revenue-generating activities.  XAI is a long term project, but I do have to earn a living too   I had been looking at a variety of avenues to bring some real funding into this project, but with the last stall-out in crypto trading activity most of those went dead or folks just left/stopped looking at crypto altogether.

We got some graphics proofs back from the designer that look fantastic, but it will be some time before he is complete with production ready designs.

I'll probably open source this project this weekend and just get the code out there for people to play with and see what the community comes up with.

I've had a lot of people asking me about IBTP.  We haven't dropped source code yet for our feature set.  But, what IBTP is doing conceptually is filtering on pchMessageStart and maintaining a directory.  You modify the message loop so that it doesn't just drop peers with a different pchMessageStart, but tags them instead.  Then in the message loop you just put a check on the flag in all of the default messages so that it doesn't exchange block inventory etc. with non-native blockchains.  That's it, its very simple.  Once you do that then its just a matter of adding whatever shared serialized payload classes you want into both node clients and message filtering in the bitcoin message loop in main.cpp.  It is very straightforward, and from that simple base you can pretty much build anything you can think of on top of it.  No side-channels or proxies or anything required, just out of the box bitcoin peering.

In our case, we actually have a future use case for masternodes - neuromining pool operations.  There is a lot of development effort between here and there, but it is an actual useful purpose for them.

I think we have to be careful to strike the right balance when it comes to the collateral amount.  I've been watching some of the latest batch of coins lately, some are lower and some are higher.  It seems that if you make it too high it seems to limit the interest and participation.  I need to put together a spreadsheet and run some numbers and see what makes sense.

Aww..i dunno about that... cross-compilation for Windows is definitely a weak spot for me

We will be dropping releases soon.  That libqtlua stuff really kicked my butt, but I figured out a way around it to get it going, and we have some cool stuff going into the coin to help broaden its appeal since the AI stuff seems to be very narrowly focused.

I want XAI to be broader as a complete nextgen FinTech platform, with the data and algorithmic stuff as a nice technical foundation, but with more end user oriented features on the surface so we can start appealing to more people.  We have something nice coming with XaiNodes, and then our in-wallet counterparty port which is my focus this week, and then rewriting the wallet using QML/QtQuick which will allow us to do a lot more cool stuff that other bitcoin-based wallets can't.  Then our Android custom rom XaiOS.  And eventually I will save up enough money to buy the XaiSat. 

We also have a pro graphics guy doing a rebrand for us with a wallet restyle and some other artwork.

My video machine is down right now, once I get it fixed I'll be able to do more videos.

I mined this on the advice of a couple of investors in my own projects.  I understand this is going to be quite the coin.  I like the numbers and I'll do your Android wallet if you want when your release is ready.  Already got my stack so don't need OTC at this time.  Been staking like a champ with no orphans at all.  Can't wait to see the roadmap and what all the fuss is about

Yes, you are missing something   Do some more exploring...

So I ran into an issue getting the Windows build to compile - more specifically getting libqtlua to "link" using mingw64.  I stayed up for 2 days straight banging my head against the wall trying every trick in the book to get it to work.  Then I realized...I can just pop the libqtlua source under the Sapience source tree and build it in directly.  So that is the approach I am trying now.

Lots of stuff in the works as this ramps up, on the marketing collateral and marketing front as well as the dev front.  Once I get the build resolved and past that roadblock we'll start rolling.