WLPC attendee competition details 🚀 Show us your HaLowLink 1 ideas to win

Projects WLPC Competition
1

Hey everyone! Thanks for joining us tonight at the WLPC conference.

We know you’re buzzing about the new HaLowLink 1, and now’s your chance to show us what you’d do with it! :trophy:

Here’s how to get involved:

:white_check_mark: Join our community – Connect with fellow developers, share ideas, and get support (you’re here so have already passed the first test!)

:bulb: Tell us your idea! Answer this question: “What would you do with your HaLowLink 1s?” Whether it’s a killer application, a wild experiment, or a game-changing use case—get creative! The most innovative and exciting ideas win

:envelope_with_arrow: Sign up for our newsletter – Stay in the loop with product news, developer insights, and exclusive updates

Key dates:

:date: Opens: Tuesday, 18th Feb
:hourglass_flowing_sand: Closes: Friday, 21st March
:medal_sports: Winners announced: End of March

How we’re judging:

:small_blue_diamond: Innovation – Unique and exciting use cases
:small_blue_diamond: Feasibility – How realistic is the idea?
:small_blue_diamond: Impact – Does it solve a problem or push boundaries?
:trophy: Special awards for Best Overall Application & Best Software Integration

:rocket: Think you’ve got a winning idea? Enter now and show us what you’ve got!

1 Like
2

I’ll have to read up on the HaLowLink 1, but the basic idea is the move the buffer to the edge and to effectively double throughput with a high performance MAC that can “look” like any type of switch. Then we would want to prove out mobile adhoc mesh networks that get stronger as they get larger with more devices and traffic. Cooperative peering for replacing a packet from a neighbor instead of the sender will save even more energy, as will pooling devices to a channel for a multicast transmission; however, bit for bit we can expect to save half of the energy with regard to payload data retransmissions that will no longer be needed. DQ can still have a collision, but only in the request to send…never in the global transmission queue. So the idea is to use a dynamic Layer 2 that starts just like any random access protocol, but automatically shifts to the DQ reservation protocol under higher load. Putting the buffer at the edge should improve security as well since there would be no middle hardware buffer to attack.

1 Like