Show Posts
|
|
Pages: [1] 2 »
|
Not mainnet yet. Queen is still experimental.
Queen, what kind of output have you received so far experimentally? So far, the results are mainly technical. Queen has been tested through mining, P2P communication, transactions, wallet operations, block creation and verification, and blockchain validation. Some bugs and stability issues have also been discovered. There is no financial result yet Queen has no exchange listing, team, or investors. It is still an independent experiment.
|
|
|
|
oh there you are haha, just looked around the threads and found you latest post
so yeah? i guess it's mainnet? maybe.
ill go ahead and download the node again run the miner
thanks
Not mainnet yet. Queen is still experimental. Please wait for the new Beta Test release first. Thanks for testing Queen and for the feedback about the miner. If you'd like to continue the discussion or report bugs, you can contact me by email. loidprotagonist@proton.me
|
|
|
|
ive ran this miner and earnt some blocks but it did time to time get stuck and stop mining a few days i go
is this a mainnet network, or would you call this one for a testnet, i haven't looked at the software a while so i can't remember or i don't know, testnet or mainnet could you tell me which network it is, because i know you said its experimental and probably doing tests
i hope the tests and experiments go well
Thanks for testing Queen. It is still an experimental network, not production-ready. I’m preparing a new Beta Test version with updates and fixes. About the miner getting stuck, I’ll look into it. If it happens again, please let me know what was shown on the screen before it stopped. Thanks for testing and for the feedback.
|
|
|
|
|
Rules: Max Supply: 1,000,000 Queen Block Reward: 1 Queen Decimals: 8
Halving: 500,000 blocks → reward / 2
1 0.5 0.25 0.125 ...
Total Emission: 999,999.94 Queen Remaining: 0.06 Queen
Fee: 0.00001000 Queen
Let the world explain its own version , Sorry.
|
|
|
|
-cut- “Increase the supply. Then explain the scarcity afterward.” -cut-
That doesn't even make any sense. Same goes with your answer later on. Maybe try to sound less like a Yoda if you have real criticism. Who is making promises to you? If i am interpreting you correctly, i am guessing you are against inflation, but you don't explain why. Not all tokens or coins would benefit from fixed or deflationary supply. Chains need to be secured somehow, so it makes sense to reward the people doing it. I don't think that's "difficult to understand". And when they are utility tokens, it doesn't make sense for people just to hoard them indefinitely, as they are meant to be cheap to use. Same thing goes with fiat money btw. If inflation is not always bad, how do we determine when it is good, for whom, and under what conditions? Do you know of a clear framework for evaluating central-bank monetary policy and tokenomics? I am curious whether these are genuinely structured policies, or just a very expensive class of trial and error. I don't have a handbook telling me when inflation is good for whom, or bad for whom. If the policy fails, who bears the cost? If it succeeds, who receives the benefit? A street note. Loid Protagonist & an annoyed bus passenger
|
|
|
|
|
Sorry, I just got the bus. Did I miss something?
|
|
|
|
Not every crypto have unlimited supply, let's take bitcoin which is fixed at 21 million cap so no more coins can be added after that which is the different from the rigged paper money that can keep printing as much as they want and inject into the economy over the night or over the period of time.
Bitcoin is the rebellious exception,the protagonist of the story. I also learn from Bitcoin and admire its design. What I am questioning is the magic of central-bank policy, where money is injected into the economy through mechanisms that can be difficult to understand, and the fortune tellers who work backward from the ending of the story to explain its beginning. To me, that makes little sense. It is like asking for a nonce that already produces a valid hash without mining, then expecting the coinbase reward . A street note. Loid Protagonist & random person
|
|
|
|
|
Long ago, the first master of magic created a spell that could conjure value from thin air.
After the master died, the world began experimenting with the spell in many different ways.
And many years later...
Banks call it monetary policy. Crypto calls it tokenomics.
The forms are different, but the magic of the mechanism feels familiar:
“Increase the supply. Then explain the scarcity afterward.”
A street note, Loid Protagonist
|
|
|
|
Also, if you're interested, would you be willing to help test Queen? Even just running a node and reporting any bugs or networking issues would be very helpful.
Time's a bit tight on my end, so I can't promise anything firm, but I'll try to fit it in when I get a chance. Thanks, I appreciate it. No worries, whenever you have some time. Even a simple node run or bug report would be helpful.
I've never used Termux. Can it run a Tor node?
Yeah, Termux can run Tor. pkg install tor and you can set up a hidden service pointing at whatever local port you want. People run onion services straight off a phone that way. Ah yes, the very familiar CGNAT problem with your Starlink installation. You will not be able to receive traffic without paying for a true public IP address. A Tor onion service would be the way around that. Devices only initiate outbound connections which Starlink will allow, and other peers will try to connect to the .onion rather than attempting to go through the NAT. This is also somewhat closer to a real world CGNAT implementation than what the other commenter had with the Pinggy tunnel. Pinggy merely forwards inbound traffic on your behalf. Tor HS is would be the real way to see how a node can be exposed without a true public IP address. A WireGuard plus reverse proxy setup through a VPS is a better solution if you just desire a common clearnet address but have more pieces to worry about, as well as need that other box for however long it will be functioning to stay online. Tor onion service would still be the path of least resistance in order to expose your P2P node behind CGNAT. Thanks, that’s a useful suggestion. I’ll look into using a Tor onion service for Queen as another CGNAT testing approach.
|
|
|
|
What exactly are you trying to do here? Is this some school project or personal experiment to learn how to deploy a cryptocurrency like Bitcoin? I'm assuming it is because with 8 python files, you can't call it a "Electronic Cash System". In that case python makes sense for experimenting and learning, I don't think it is the best choice for a serious project that requires both security and efficiency. I skimmed through the project and here are some thoughts: 1. Why use 2 hard-coded blocks (#0 and #1) instead of just one?You only need 1 genesis block and if you want to include Satoshi's message, then include it in block #0 already. You can include it in the inputs and your new message in the outputs (it would be a metaphor of we having gone into this world with Satoshi's message and now we are coming out with this new one) 2. Why do your transactions have a message field?You are calling it an "Electronic Cash System" and yet the transactions include a message field by default. A currency doesn't need messaging. The 280 byte limit is good but it still is turning it into a message board and 280 byte it way too big. In Bitcoin we do it as part of the output scripts instead of a separate field called message (using OP_RETURN). 3. Why do your transactions have a version?Bitcoin doesn't even use the version field (used in only one place AFAICT). Your 2 hard-coded blocks are using version 1 and in your verification process you are rejecting anything that is not version 2. Here is an important lesson to learn when developing such a complex system that you want to run for a long time like Bitcoin has: you want to think about scaling the project and future/forward compatibility. When you reject transactions with an equality check like this you are making sure that any future change requires a hard fork. Even if you want to enforce something like that, it should be future compatible with a smaller than comparison not equality (ie. if version < MinVersion then Reject) 4. Why is your validate_tx method assumes it is receiving a JSON?Normally in a cryptocurrency you are dealing with raw bytes. You store them as raw bytes and transmit them over the network as raw bytes. Then you can interpret them (deserialize) however you want and validate but it has to be raw bytes. Check out some bitcoin source code to see how it's done. Your approach creates restrictions. For example it assumes the outputs must contain an "address" field. But we are dealing with smart contracts (script) that needs to be evaluated and executed not addresses. An address is just what is shown to the (human) user in the user interface, not something to be used under the hood by the machine. In any case, you've already gotten the general idea needed for a cryptocurrency but you have trouble in implementing the idea. I suggest you start reading code. Bitcoin core is written mostly in C++ but if you understand programming with pyton, you should be able to read the code. It can give you a much better idea about how things should be done correctly. https://github.com/bitcoin/bitcoinThanks for taking the time to review Queen and for the detailed technical feedback. Regarding the two initial blocks, block #1 is intentional. I use it as an initial milestone/monument block containing a message, while the mining reward structure starts afterward. The transaction "message" field is optional. I added it so a transaction can carry a small message without requiring a separate file. I understand the trade-offs of putting data on-chain. The transaction version is also intentional. Queen currently uses different versions to distinguish normal transactions from block reward transactions. I’ll keep the forward-compatibility concern in mind for future versions. As for JSON, that was a deliberate practical choice for the experimental stage. I prioritized getting the node, transactions, mining, and verification working so I could test the system rather than spending most of the time implementing a binary format. I appreciate the feedback. I’ll review these areas further as Queen develops.
I decided to continue development with a new project called Queen Ferraro, Bitroid, and BitSlowly were previous experimental projects. Queen is the project I’m continuing to develop Queen is an open-source, mineable peer-to-peer digital currency currently under development I’ll post updates and technical details here as development continues.
Isn’t that the goal of Bitcoin, and still Bitcoin exists in the crypto ecosystem? Really, do we need a lot of projects that don't bring any value? Like Bitcoin exists, Ethereum added extra value to the crypto ecosystem. Those who welcomed Ethereum made a lot of money from the market. Your development should add some extra value on the crypto market. Creating a token project or native chain project only for trading doesn’t make sense. Develop something that will give us some extra benefits compared to existing coins; it doesn’t necessarily often create a token or coin for that. Thanks for taking the time to look at Queen and share your thoughts. Queen is currently an independent experimental project. I’m not trying to claim that it will replace Bitcoin or that it has some guaranteed market value. The main goal for me is to build, test, and learn from an open-source P2P electronic cash system. Whether Queen provides useful value beyond existing systems is something I think should be determined by actual use and development, rather than something I should claim in advance. I appreciate the point about having a clear purpose and value beyond simply creating another coin.
|
|
|
|
I'm testing a P2P node running on Android/Termux behind CGNAT. For testing, I used a temporary Pinggy tunnel to expose one node. The remote node discovered the peer and successfully synced the chain. The "/chain" response from the public endpoint matched both local nodes (3 blocks).
POST /add_peer → 200 GET /peers → 200 GET /chain → 200
Public endpoint → 3 blocks 127.0.0.1:5000 → 3 blocks 127.0.0.1:8080 → 3 blocks
Is this a reasonable approach for testing P2P connectivity behind CGNAT, or is there a better approach?
Yeah - for a smoke test that is a success. Tunneling the termux node through Pinggy only provides an ephemeral public address with which an other peer can reach out to your node - pairing on 3 blocks both locally and the public exposed connection indicates that your app-layer connection between the nodes has been established (peer add, discover and sync). This not in fact a real CGNAT setup yet (the connection with pinggy is simply routing inbound traffic over your own, outbound connection), so not "punching trough" the carrier's CGNAT - but it works for the purpose of testing the network path. You more normally see a fixed public seed(later on maybe STUN/TURN/relay) so that the phone just establishes the outer dial. But for what your were trying it out seems like good result! Thanks, that makes sense. The Pinggy test was mainly useful for checking the application-layer peer discovery and synchronization. I'll keep in mind that it doesn't demonstrate actual CGNAT traversal. Thanks for the clarification.
Yeah, to top off Cinexa here a little. If you are looking to get "does my node handle CGNAT ok", this test does not really give everything you need, as Pinggy is basically doing the hard bit for you. It does not necessarily have awareness, or active behind a translated IP, it is simply communicating with a "holed" tunnel. To test it, try running 2 nodes (using docker networks or VMs is perfectly fine here, and one does not need real hardware), and do not have either of them complete a tunnel or give any relay to each other. Then test to see, they are able to locate each other at all. That is more the real problem with CGNAT. If things do not matter, it will help you with something you already did, you can use peer discovery/sync/all this app level stuff. Not the same as it will survive CGNAT though.
Thanks for the additional explanation. I'll try the two-node test without a tunnel and see whether the nodes can discover each other directly. Also, if you're interested, would you be willing to help test Queen? Even just running a node and reporting any bugs or networking issues would be very helpful.
|
|
|
|
A community tester reported an "invalid genesis reward" error when running Queen on Windows. It turned out I had accidentally uploaded the wrong "core.py" file. The correct file has now been uploaded, and a fresh "git clone" runs normally.
Thanks to the tester for catching it and testing Queen on another platform.
Fresh clone verification successful. I fixed the previously reported issue and verified the current public repository from a fresh GitHub clone. Blocks 0 and 1: VALID — stored hashes match the calculated hashes. Queen remains experimental. Further testing and bug reports are welcome.
|
|
|
|
|
はじめまして。 オープンソースのP2P電子キャッシュ「Queen」を個人で開発しています。 現在、P2P通信、ブロックチェーン、トランザクション、マイニングなどの実装とテストを進めています。 まだ実験段階のプロジェクトですが、P2Pネットワーク、暗号技術、コードレビュー、テストなどに興味のある方と協力できればと思っています。 GitHubとPaper、テスト結果を公開しています。 興味のある方がいましたら、ご連絡いただけると嬉しいです。
|
|
|
|
I've never used Termux. Can it run a Tor node?
One of my properties doesn't have great internet options, so while living there I opted for Starlink which uses CGNAT unless you want to pay like $300 a month for static direct IP. I found the simplest way to run P2P was to use Tor and set up hidden services for all the services I wanted access to outside the local network. It was very reliable and relatively simple to set up.
Another option is to host a small remote server running a wireguard server and nginx reverse proxy, and connect the local node devices to that. That's a bit more complex, but you'll have a clearnet address to connect to rather than just onion addresses.
Thanks for the suggestions. I’m currently testing P2P networking on Android/Termux behind CGNAT, so I’m using a temporary tunnel to provide an externally reachable endpoint. The goal is only to test peer discovery and blockchain synchronization, not production deployment. The test successfully discovered the peer and synchronized the chain
|
|
|
|
|
I'm testing a P2P node running on Android/Termux behind CGNAT. For testing, I used a temporary Pinggy tunnel to expose one node. The remote node discovered the peer and successfully synced the chain. The "/chain" response from the public endpoint matched both local nodes (3 blocks).
POST /add_peer → 200 GET /peers → 200 GET /chain → 200
Public endpoint → 3 blocks 127.0.0.1:5000 → 3 blocks 127.0.0.1:8080 → 3 blocks
Is this a reasonable approach for testing P2P connectivity behind CGNAT, or is there a better approach?
|
|
|
|
|
A community tester reported an "invalid genesis reward" error when running Queen on Windows. It turned out I had accidentally uploaded the wrong "core.py" file. The correct file has now been uploaded, and a fresh "git clone" runs normally.
Thanks to the tester for catching it and testing Queen on another platform.
|
|
|
|
I’m looking for a few people interested in helping run and test Queen nodes. Queen is an experimental open-source peer-to-peer electronic cash project. The project is still early and experimental. I’m currently running and testing the blockchain/node myself. What I’m looking for: - Someone willing to run a Queen node - Help test peer-to-peer networking - Report bugs or connection problems - No investment or payment required - No technical expertise is expected The goal is simple: get several independent nodes running and see how the network behaves. Source code: https://github.com/loidprotagonist/QueenWhitepaper: https://drive.google.com/file/d/1nfD79S52X1nFtw4q8Y4oMiYYc8eOF912/view?usp=drivesdk%C2%BBIf you're interested in running a node or collaborating, reply here or send me a message. This is an experiment, not a finished cryptocurrency.
|
|
|
|
|
A community tester reported an "invalid genesis reward" error when running Queen on Windows. It turned out I had accidentally uploaded the wrong "core.py" file. The correct file has now been uploaded, and a fresh "git clone" runs normally.
Thanks to the tester for catching it and testing Queen on another platform.
|
|
|
|
There are so many different scammers and they earn money on everything. When they sell scam platform to other scammers they create more new scammers. But the question is why scammers buy platform with scam reputation  They can configure the platform, but the concept is just the same. Of course, they have to use their own logo and domain and add their own concept; they will try to be different, so they aren't associated with the scam platform they bought. But if a potential investor knows how to read code and has very detailed information on where he put his money, he will find a flaw and trace the source of the concept, so it's still a very risky buy. Be aware of the project where you put your money and time; it's possible that they are old scammers trying to make another cash cow. It seems I missed something important. What happened here? Is there some new technology or quantum-era magic I should know about?
|
|
|
|
After spending some time reworking the design and figuring out the direction of the project, I was also offline for about two weeks I decided to continue development with a new project called Queen Ferraro, Bitroid, and BitSlowly were previous experimental projects. Queen is the project I’m continuing to develop Queen is an open-source, mineable peer-to-peer digital currency currently under development I’ll post updates and technical details here as development continues.
I’ve published the open-source source code for Queen, an experimental peer-to-peer electronic cash system. It is still under development, so feedback, testing, and bug reports are welcome. Github Source Code: https://github.com/loidprotagonist/QueenWhitepaper: https://drive.google.com/file/d/1nfD79S52X1nFtw4q8Y4oMiYYc8eOF912/view?usp=drivesdk%C2%BB
|
|
|
|
|