Jump to content


Dev Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


domob last won the day on September 6

domob had the most liked content!

Community Reputation

108 Excellent


About domob

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. domob

    Xaya Rich List

    The difference you see is probably due to coins left over from the HUC snapshot that were burned. Due to some rounding that was done when the HUC/CHI rate was determined, we needed around 14 CHI less than what was allocated by Andy. I burnt the remaining coins in c90cd16b4caca293b71f75361d61ac35de1e902db020e0cc7729170a4087f266. Also note that in theory everyone else can also burn coins, and miners can choose to get a smaller than allowed block reward - so while I don't think any of that happened (yet), it is perfectly possible to get a smaller actual money supply than what is in theory available.
  2. domob

    Xaya Rich List

    I made it to spot #2! :D Although only for coins that are still to be distributed to presale participants that didn't yet give their addresses, unfortunately. Spot #1 is the team's multisig address that used to hold the premine (I'm sure you know that, though) - there was another transaction from it yesterday, and what is left now is the 10% team coins.
  3. domob

    Upcoming Hard-Fork - Information

    For changing the ports on testnet (or regtest for that matter), you need to put them below a [testnet] line or change them to testnet.rpcport, I think (or perhaps the other way round, rpcport.testnet).
  4. Yes, you can do that, of course. That's basically what libxayagame does itself - but there are quite a few tricky cases to think about (like missed ZMQ notifications), so you need to be careful in developing this part. If there is any kind of framework for calling C functions from NodeJS or the other way round, you may be able to use libxayagame to simplify things. But if not and you want to talk to the daemon directly, it is certainly doable as well.
  5. You mean, to develop the actual game daemon in JavaScript (not the frontend)? No, I do not have plans for that. However, I am working on a wrapper that makes it easy to use libxayagame from any language that has interoperability with C. I do not know if that applies to JavaScript, to be honest. But in general, I think you should try to avoid redoing what libxayagame does yourself. We can certainly discuss what methods there are to use the library from JS. (I personally like JavaScript as a language due to its functional concepts, but have only used it for web development and would not really think about using it to write a backend daemon.)
  6. Yeah, that is true - although it would at least give the ASIC manufacturers an advance warning of all algorithms at once. But honestly, I think at the moment that forks are not too costly for a small network like Xaya (at least if done once or twice per year, not every week). So to me the most important aspect of the "cost" side for changing algorithms is the future maintenance burden that is imposed. Thus I think we should go for a single algo change rather than adding ten algorithms immediately.
  7. Since Xaya is not just a blockchain project but a platform for blockchain games, we are not only working on the core blockchain infrastructure but also additional layers that make it easy to develop fully decentralised games. The first step in this direction is the game-specific ZeroMQ interface we designed, whose main parts are already implemented and tested in the Xaya Core daemon. Using this interface directly, however, still requires messing around with potentially unreliable ZMQ notifications and handling of blockchain-specifics like reorgs. Thus, we are also building libxayagame: A library that interfaces to the core daemon through the ZMQ interface and handles all the blockchain-specific processing. This makes it super easy to develop fully decentralised games on the Xaya platform, without any prior blockchain experience or knowledge. All you have to do to implement a game is to provide functions that implement your game rules; namely by computing a new game state from the old state and a set of moves. The library then handles all the rest for you. This is still very much a work in progress with lots of missing pieces before it can be used in production, but it can already be used in development and early testing. So if you are interested in developing a game on Xaya, I strongly encourage you to take a look at libxayagame and the integrated example game "Movers". It can probably save you a lot of messing around with ZeroMQ, blockchain reorgs and other stuff.
  8. Apart from managing the associated fork, this is not very hard - assuming, of course, that the algorithm we want to use is readily available as free code we can just use. And of course by doing so, the complexity of the codebase grows forever - every algorithm that was ever used needs to stay in the code forever. That's the main thing I want to avoid if it is not really necessary. I'm not sure which last sentence you mean, TBH. But if you mean the general idea of rotating algos, then yes, in principle that's a solution - but it comes with a cost, namely ever-increasing code complexity (and maintenance burden) and regular forks. My opinion is that it is not a "no brainer" (as many seem to think) to trade this for the dubious benefit of being ASIC-free for a couple of months. But as I said previously, if the general consensus is that it is worth this cost, then I'm happy to implement it.
  9. Many know already my opinion on this, but let me just state it here once more for those who do not: I believe that all this "ASIC resistance" stuff is both impossible to achieve and also not really relevant. ASICs will always be built as long as it is economically feasible, and there's nothing that can be done against it except for changing the algorithm over and over again. And especially for Xaya, there is no real harm in having ASICs on the network - since the majority of hash rate is in merged mining anyway, it would not even hurt security (much) if a single guy with an ASIC controlled all the stand-alone mining. However, I agree that it may be useful for community purposes (even if there is no technical reason) to allow people with GPUs (including gamers) to mine Xaya. Implementing an algo change is not too hard, as long as we decide on what it should be and there's an existing simple C/C++ implementation that we can just plug into Xaya - so I'm happy to do this. Please keep in mind that there are many altcoin projects whose only "innovation" is a change in mining / ASIC-resistance - think of Litecoin (which was the number-two cryptocurrency for a long time) or Bitcoin Gold (the second-largest Bitcoin fork, behind only a project that didn't even add something and just removed features). It is clear that those projects keep talking about how important the details of the mining algorithm are and how fancy their algorithms are. In contrast, we at Xaya have real blockchain innovations to concentrate on, so that the mining algorithm is only a minor detail in my opinion.
  10. domob

    Need opponents for testing

    Just to clarify this bit: The XAYA platform itself is not tied to any particular OS (and especially not Windows in particular, I myself don't have a Windows machine either). For individual games it all depends on how they are developed, of course. But in the XAYA model, there will typically be two parts to any one game: One backend part that runs the game logic and interacts with the blockchain and a frontend that just displays everything nicely and lets the users generate moves by clicking buttons. I expect that most games release the backend part as open source and in a way that can be run cross-platform, while the frontend may be prioprietary and tied to Windows, for instance (but again, that's totally up to the game developers).
  11. domob

    Add Xaya to Trezor

    For the web wallet, I think you also need to run (and specify in the JSON file) a "backend server". Also, I was told that you don't typically get on that web wallet anyway as an altcoin - only a selected few are. Or is that wrong, are all those zillions of "supported coins" available from there?
  12. domob

    Interest in mmo Pokemon-like game on Xaya

    Unfortunately not much yet. There are rather technical descriptions about Xaya's general model for games as well as the core daemon's ZMQ interface (created specifically for the gaming usecase). I suggest that you start by reading at least the first page to get an understanding of how games are supposed to work. For the actual implementation, we are right now in the process of implementing a wrapper library that takes care of interfacing to the core daemon (including the ZMQ interface described) for you. In principle, when you use it, all you need to do is "just" write functions that implement the particular game-state processing of your game. The libxayagame repository is available to the public already, although still very much in development. But you can take a look at it and the "Movers" example game included. If you decide to start actual development after looking through these resources, I suggest that you talk to us first to discuss your rough plan. I'm happy to schedule a video call on Google hangouts, for instance. I think that will be useful to align your development to our future plans and make sure you are not wasting time on anything that might be obsoleted in the future (and things like this). We certainly do have a lot of more improvements coming in the future.
  13. domob

    Add Xaya to Trezor

    Well, some. I did some more research, and it turns out that integration with Trezor is likely a "two tier" process. The first step is, I think, really just adding this JSON file (and proper testing). That would allow users to create Xaya addresses and work with them using the Trezor command-line tools. The second step is to integrate Xaya with a Trezor-supporting wallet, which enables actually managing the wallet easily. While the first step would be relatively easy to do, the second requires more work on our side. So at the moment, we decided that just going for the first step is not worth it, because that would essentially allow power users at best to do anything at all with it. However, we do have plans to implement Xaya support in Electrum - which would enable full Trezor support in the future.
  14. domob


    We are and were aware of the rising trend of 51% attacking "minor" coins. Mainly because of that, we designed our custom triple-purpose mining scheme: It combines the best of merged mining and stand-alone mining - merged mining secures the chain while the stand-alone mining part still builds a mining community and distributes coins widely. So to answer your question: Merged mining makes a 51% attack very hard. Xaya is merge-mined by at least one major Bitcoin mining pool at the moment, which gives it a SHA-256d hash rate of 1.5 EH/s - to put that into perspective, that is 3.75% of Bitcoin's hash rate. In the future, we hope that we can get even more miners on board as well, and rise that even further. I do not know what hash rate BTG had during the attack, but with the amount of hashing Xaya has, it certainly takes more than some random guy renting GPUs in the cloud.
  15. domob

    Interest in mmo Pokemon-like game on Xaya

    Sounds great! If you decide to try the XAYA platform, you would be one of the first building games for it - and we are happy to support you as much as we can.