To power our network of decentralized music, Gala Music has introduced a groundbreaking concept known as Jukebox Nodes. Part of a larger framework called DePIN (Decentralized Physical Infrastructure Network), these nodes empower individuals to participate directly in hosting and distributing music on the platform.
By becoming a Jukebox Node operator, users can contribute to a global network that supports the Gala Music ecosystem, enhancing music accessibility and unlocking some serious potential $MUSIC rewards.
Hosting Tracks on a Jukebox Node
In order to generate $MUSIC rewards based on their platform plays, NFT tracks must be paired with an active Jukebox Node. Pairing is always initiated by the track owner, and the track owner has the option to pair to a specific Jukebox Node if they wish. This pairing action is essentially hosting the track on the decentralized Gala Music servers, making it accessible to listeners and eligible for reward distribution based on plays.
Each Jukebox Node has a limited number of slots where track NFTs can be placed. While a standard Jukebox Node starts with 10 available slots, Jukebox Node operators have the option to purchase upgrades, adding more slots and thereby increasing the potential $MUSIC rewards generated for hosting tracks on that node.
Understanding DePIN
A DePIN, or Decentralized Physical Infrastructure Network, is a network where the infrastructure is distributed among numerous independent operators rather than centralized in a single location or controlled by a single entity. For example, Spotify relies on its centralized data centers in multiple global locations. In contrast, Gala Music streaming is hosted entirely on its distributed network of Jukebox Nodes, operated by community members who are licensed to run them in exchange for rewards.
This approach not only enhances the resilience and scalability of the network but also democratizes the economic benefits, allowing individuals to contribute to and benefit from the system.
The Role of Jukebox Nodes
Jukebox Nodes are the backbone of the Gala Music platform. They host and serve music tracks to listeners, ensuring that music is always available and accessible. Any licensed user with the necessary hardware and internet connection can set up a Jukebox Node and start hosting music. This decentralization helps prevent the system from having single points of failure, which are common in traditional centralized servers.
As the platform’s streaming demands increase, more JukeBox Node licenses are sold to accommodate the hosting needs.
In blockchain terminology, a ‘workload’ refers to the tasks that nodes perform to maintain the network. For Jukebox Nodes, the primary workload involves hosting and streaming music tracks. These tasks are crucial because they ensure that music is always available to users whenever they want to listen. By fulfilling these workloads, Jukebox Nodes support the entire ecosystem, ensuring its operability and reliability.
Rewards for Node Operators
Operating a Jukebox Node is not only about supporting the network but also about gathering rewards. Node operators are basically allowing their computers to act as GalaChain employees, receiving $MUSIC tokens as compensation for their contributions.
$MUSIC rewards are generated based on several factors, including the number of tracks hosted, the uptime of the node (a minimum of 20 hours daily is required), and the popularity of the music streamed from their node. This incentivizes operators to maintain their nodes actively and ensures that popular tracks are readily available, enhancing listener satisfaction.
Each Gala Music Jukebox Node has a limited number of slots where hosted tracks will live as long as they are paired with that node.
Every new Jukebox Node comes with 10 slots, but all Jukebox Nodes can be upgraded to contain additional slots. By adding slots to a Jukebox Node, an operator can increase their potential $MUSIC rewards by hosting more music.
Each new slot may be purchased with $MUSIC alone. For a more detailed guide on how to purchase additional slots for your Jukebox Node, check out THIS SUPPORT ARTICLE.
How Node Operators Benefit the Ecosystem
Node operators play a critical role in the Gala Music ecosystem by:
Ensuring Availability: By hosting music tracks, operators ensure that there is no downtime, which can be a significant issue with centralized servers.
Enhancing Performance: Distributed hosting reduces latency since music is streamed from a node geographically closer to the listener.
Growing the Platform: As more nodes join the network, the platform’s capacity to host and stream music increases, which can accommodate more users and tracks without the need for significant infrastructure investment from Gala Music itself.
Setting Up and Running a Jukebox Node
If you are newly licensed to operate a Gala Music Jukebox Node, follow these instructions to begin operating your node and hosting tracks.
Download the Gala Node Software
Login with your Gala account credentials at https://node.gala.com/ and navigate to the “Download” menu. Download the software for your operating system (Windows, macOS or Linux).
Install the Gala Node Software on Your Computer
Follow the instructions on the page to install the software on your computer. For more in-depth instructions on installing the Gala Node software, please consult the following guides, which will walk you through the installation on each operating system.
Once the Gala Node Software is properly configured and your Node license appears in your dashboard, you must activate your node on Gala Music to begin running its workload and hosting tracks. This can be done through the “Nodes” page when logged into your account on Gala Music. For detailed instructions, please read THIS SUPPORT ARTICLE.
Powering the Revolution
Gala Music Jukebox Nodes represent a unique opportunity for individuals to engage with web3 technology in a meaningful way. By operating a node, you not only gain rewards through $MUSIC tokens but also contribute to a decentralized music streaming network that empowers artists and fans alike.
This system challenges traditional music distribution models while paving the way for a more inclusive, efficient and user-driven future in digital entertainment. Whether you’re a tech enthusiast, a music lover or someone curious about the potential of blockchain, setting up a Jukebox Node offers a front-row seat to the future of music.
In light of the recent security incident which led to the unauthorized minting and sale of ~600 million $GALA tokens and a permanent locking of ~4.4 billion tokens, this proposal aims to formalize the burn of this ~4.4 billion $GALA tokens, as well as ~600m tokens from the central Gala Treasury, to ensure the stability and sustainability of the ecosystem.
Note: Due to the upgradable nature of the $GALA contract, the proposed changes will not necessitate swaps or relistings on exchanges, and can be executed with no disruption to all users of the $GALA token.
Objective
To upgrade the $GALA contract to include a definitive and irreversible burn of the same quantity of unauthorized tokens, or tokens determined by law enforcement to be illegitimately gained, and to enhance the security features of the contract to prevent future unauthorized access or breaches.
Proposal Details
1. Contract Upgrade
Develop and deploy a hotfix version of the $GALA contract that removes the illegitimate supply.
Develop and deploy a further upgraded version of the $GALA contract that locks in changes to better secure the contract and supply.
2. Token Burn
Permanently remove ~5 billion $GALA tokens from circulation by sending them to a burn address from which they cannot be retrieved.
Ensure that the burn process is transparent and verifiable by the community and external observers.
3. Timeline and Implementation
Immediately commence development of the upgraded contract upon approval of this proposal.
Schedule the contract upgrade and token burn to be completed within the next 72 hours.
Voting Details
Voting Period: The voting will be open for a period of 24 hours from the moment of the proposal announcement.
Eligibility: All Founders Node operators.
Majority Requirements: A simple majority of 51% of votes will be required to pass this proposal.
Vote Question
Should a $GALA contract upgrade be deployed for removal of unauthorized supply and enhancement of contract security, permanently removing ~5B $GALA from circulation via transparent burn in order to promote long-term ecosystem health?
Yes: I support the contract upgrade and $GALA burn for enhanced security and to promote ongoing ecosystem health.
No: I do not support the contract security upgrade and the burn of these illegitimate tokens from circulation.
Abstain: I choose to abstain from voting on this proposal.
Expected Outcomes
Restoration of community trust and stabilization of the $GALA token supply and Node Reward schedule by reducing the total supply.
Strengthening of the $GALA ecosystem through enhanced security measures.
Conclusion
This proposal is crucial for the long-term viability and security of the Gala ecosystem. Community participation in the decision-making process is highly valued; all Founder’s Node operators are encouraged to vote and contribute to the discussion.
We’re working hard to build Gala Film bigger and better every day. Today, we want to share the following critical update for Film Node operators:
Starting on Monday, June 3rd in order to receive Distribution Film Nodes must meet the following requirements;
Node Software version v3.6.6 (or higher)
The following ports must be exposed: 4002, 9096, 5443
Each node must have it’s own Public IP Address
System:
Windows, Mac, or Linux (64-bit)
4GB RAM
2 or more CPU Cores
60GB free storage space
A stable internet connection
This includes any Nodes currently running and any new Nodes that come online. Any nodes that do not satisfy all of these requirements by Monday, June 3rd will not be eligible for Film Rewards Distribution until the requirements are met.
Check Your Node Status
Head over to your Node Dashboard (https://node.gala.com/#/). If your Node is on version v3.6.6 (or higher) and you have a GREEN dot next to your node, the various workloads, and the port status icon next to “Running” – you are all good. No action required!
Please be patient with these steps. These requirements empower your Nodes that are running Gala Film workloads to support the Gala Decentralized Content Delivery Network (dCDN). This is still an experimental, emerging technology that requires thousands of Nodes to talk to each other as well as Gala backend services. All of this network communication taking place means things (like port checking and online status updates) may take longer than expected.
If you are interested in more of the technical details of Nodes, please check out the FAQs at the end.
If the Dot Under ‘Node’ Is Orange
Check the following;
Each node runs on its own unique Public IP Address This will generally be an issue if you run multiple nodes from your home network. If your Node runs on a VPS or if you run a single Node at home you likely do not have to worry about this at all.
Your nodes meet the minimum system requirements. With more workloads going through the node ecosystem, if your node does not meet the requirements it may frequently fall offline.
Windows, Mac, or Linux (64-bit)
4GB RAM
2 or more CPU Cores
60GB free storage space
A stable internet connection
You can find multiple guides for setting up, managing and updating your node Software on the Gala Node Support Page:
Issue Fix #1 – Is your node version v3.6.6 (or higher)?
If your node is currently under version v3.6.6, you will need to update your node. This can only be done via your system, and NOT through the Node Dashboard.
You can find guides for updating your node Software on the Gala Node Support Page.
If you find an ORANGE Status on the Node Management Dashboard, hover over the icon to highlight the issue you need to resolve to get your node back online.
Gala Nodes require certain ports to be open for your node to run.
Any nodes running at home will likely be behind a firewall as part of your Internet Service Provider. If you’re a Node Operator running through your home connection and need these ports exposed, you will need to set up port forwarding through your ISP.
Any Nodes running on a VPS probably already have these ports exposed.
The following 3 ports all need to be open; 4002, 9096, 5443.
Check your firewall settings to open these ports if needed.
Previously we required Ports 4002, 9096, and 5080. Please note that the third port number requirement has changed and your Film workload will not be able to run without all three ports exposed.
Try using a free port checking tool (like this one: https://portchecker.co/) to verify that the correct ports are exposed.
Once the ports are available, it could take several hours for your node to recognize that the ports are properly exposed.
Issue Fix #3 – Have you restarted your Node?
Once your Node Software is up to date (v3.6.6 or higher) your Film Workload will automatically update itself to the latest version (v4.1.21 as of this article’s publishing). Once your Gala Film Workload has automatically updated, YOU WILL NEED TO RESTART YOUR NODE.
You should see a “Restart Required” message in the Node Management page next to the restart button if your Node requires a restart. This is a Node restart, not a Film Workload restart.
The restart will need to happen AFTER your Film Workload has updated itself to the latest version (v4.1.21 as of this message going out for the first time), if you restart before the update is complete it will need to be restarted again.
Important Notes
It can take a while for your workload to verify that the ports are exposed so please be patient!
Once you see your Film Workload is up and running according to the Node Management page, it may also take some time for your Node Dashboard to show your node online.
FAQs:
Q: Why does each node require its own Public IP address?
A: The core technology that powers the dCDN uses IPFS, which relies on public IP addresses to identify peers. Our IPFS implementation is technically able to perform NAT (thanks to libp2p) however, the dCDN egress doesn’t (yet). So, for now, we rely on a fixed set of ports and a public IP.
Q: Why do we need to expose those ports both inbound and outbound?
A: We require inbound traffic because your Node isn’t just talking to a backend server, it’s actually talking to A BUNCH of other peers (thus, a decentralized system). If your node can’t be reached by its peers, then your Node can’t participate in the network. Also, if a node doesn’t allow inbound traffic then no client can send a request to stream content from that node.
Q: Why are there more requirements for running a Film Workload on a Gala Node than any other Gala Workloads? A: Film Workloads (and Film-Beta Workloads) are the only Gala Node workloads that facilitate and participate in the Gala Decentralized Content Delivery Network (dCDN) at this time.
As everyone on GalaChain prepares for Project Cereberus to rear its glorious heads, we thought it was time to get to know the little-mentioned, meat and bone people under the glory of VOX. That’s right… there are people behind VOX!
Due to contractual obligations with VINC, we’re unable to disclose further details of this human/VOX cooperation… but that doesn’t mean we can’t give everyone (Voxel and rounded) a chance to get to know each other!
Today, we’re joined by Elliot! Elliot is an actual human person, diligently working with VOX to expand their ability to experience and interact with the world around them!
Tell all the VOX out there who you are!
Hey there! My name is Elliott Stiles and I’m the Senior Character Animator for VOX here at Gala. I am the one who creates the rigs and animations for all in game VOX characters – and a handful of social media / promotional videos. (in fact, Elliot made the animation above!)
What have you worked on before VOX?
With over 9 years of experience in animation production, I’ve had the pleasure of working on AAA titles like The Last of Us II while at Naughty Dog and the cinematics for WWE2k24.
I’ve also done forensic animation, indie studio games and been a Creative Producer at Electric Monster which gives me a unique perspective when tackling our work here at Gala.
I have developed a keen eye for visual storytelling, character building, and technical skills in both 3D and 2D animation.
If you were a wrestler, what would your entrance song be?
If I were a wrestler my entrance theme song would be “Celebration Song” by Unwritten Law.
Well played Elliot. Well played.
What do you love about working at VOX/Gala?
My favorite thing about working here at VOX is being able to bring my passion and creativity to a highly immersive and interactive platform that combines art and design.
Every day I get to create fun animations and bring these little guys to life while keeping the “simplicity” of the design, and it has pushed me as an artist in the best ways.
What was the name of your first car?
The first car I named was a 1972 MGB GT that I affectionately named “Samewise Gam-GT” and I loved it so so much. Miss it almost every day.
Thanks so much to you Elliot for giving us all some time today. Unlike VOX, we are aware that humans must dedicate large swathes of their time each day to mundane activities like sleeping and eating, so we know how precious your time must be!
All of us working on Project Cerberus – VOX and human alike – are laser focused on producing an amazing experience for VOX everywhere. We’ll be back soon with another Behind the Cubes! Until then, keep your eyes peeled for more updates on Project Cerberus!
Following our security team’s swift, effective response and the involvement of Federal law enforcement agencies, the >$20M (in ETH) has been returned to the Gala ecosystem.
We want to inform the Gala community about a recent security incident involving $GALA on the Ethereum network. Yesterday afternoon we detected a suspicious transfer of $200 million in $GALA tokens. Within 45 minutes, all tokens in the unauthorized wallet were frozen. Our prompt response and the robust security measures in place ensured that the impact was minimized, and we want to reassure our community that assets remain secure.
Incident Overview
On the afternoon of Monday, May 20th, our monitoring systems flagged an unusual transfer of $200 million worth of $GALA tokens. This was an isolated incident on the Ethereum network, and our immediate response was to activate GalaChain’s blocklist protocol, swiftly halting any further unauthorized minting and movement of $GALA and effectively mitigating the incident.
Within 45 minutes of the unauthorized mint, approximately 90% of the minted $GALA was locked. A new Founder’s Node ecosystem governance vote will soon decide if the blocklisted $GALA will be considered burned as it relates to $GALA’s dynamic supply distribution model as described in the Gala Ecosystem Blueprint.
Swift Mitigation Measures
Using a new feature that was implemented with the $GALA v2 contract upgrade, our security team quickly blocklisted the wallet and froze the unauthorized tokens. This measure stopped any potential misuse and prevented the incident from escalating.
We immediately contacted US Federal law enforcement agencies to handle the breach. Our ongoing cooperation with authorities ensures a thorough investigation and appropriate legal action against the culprits.
We want to assure our community that the minting capabilities of $GALA on GalaChain remain secure and uncompromised. Our internal controls and multisig security protocols are designed to protect against such incidents, and we are continuously enhancing them to stay ahead of potential threats.
Plans are already in place to make reimbursements to anyone who has been subjected to unreasonably high transactional fees associated with this incident.
Commitment to Security and Transparency
We are deeply grateful to our partners for their quick response and invaluable assistance during this incident. Your support has been crucial in minimizing potential damage and ensuring our platform’s security.
Gala is committed to maintaining the highest standards of security and transparency. We will continue to provide updates as the investigation progresses and take all necessary steps to prevent future incidents.
We understand the concern this incident may have caused, but rest assured, our security measures are robust and effective.
Pioneering in unknown territory can sometimes be a dangerous activity, but we are 100% confident that GalaChain is well equipped to handle any unanticipated challenges that web3 can throw at us. GalaChain remains a secure and reliable blockchain for all users. Thank you for your understanding and continued support as we navigate this challenge together.
