Authors:
(1) Clayton W. Kosonocky, Department of Molecular Biosciences, The University of Texas at Austin (clayton.kosonocky@utexas.edu);
(2) Aaron L. Feller, Department of Molecular Biosciences, The University of Texas at Austin (aaron.feller@utexas.edu);
(3) Claus O. Wilke, Department of Integrative Biology, The University of Texas at Austin and Corresponding Author (wilke@austin.utexas.edu);
(4) Andrew D. Ellington, Department of Molecular Biosciences, The University of Texas at Austin (ellingtonlab@gmail.com). Table of Links Abstract & Introduction
Methods
Results and Discussion
Determining Whether Canonicalization Impacts Search Behavior
Explanation of Search Behavior & Drawbacks, Future Improvements, and Potential for Misuse
Conclusion, Acknowledgements, Author Contributions, & more.
Supplementary Figures Supplementary Figures This paper is available on arxiv under CC BY-NC-SA 4.0 DEED license. Authors: (1) Clayton W. Kosonocky, Department of Molecular Biosciences, The University of Texas at Austin (clayton.kosonocky@utexas.edu); (2) Aaron L. Feller, Department of Molecular Biosciences, The University of Texas at Austin (aaron.feller@utexas.edu); (3) Claus O. Wilke, Department of Integrative Biology, The University of Texas at Austin and Corresponding Author (wilke@austin.utexas.edu); (4) Andrew D. Ellington, Department of Molecular Biosciences, The University of Texas at Austin (ellingtonlab@gmail.com). Authors: Authors: (1) Clayton W. Kosonocky, Department of Molecular Biosciences, The University of Texas at Austin (clayton.kosonocky@utexas.edu); (2) Aaron L. Feller, Department of Molecular Biosciences, The University of Texas at Austin (aaron.feller@utexas.edu); (3) Claus O. Wilke, Department of Integrative Biology, The University of Texas at Austin and Corresponding Author (wilke@austin.utexas.edu); (4) Andrew D. Ellington, Department of Molecular Biosciences, The University of Texas at Austin (ellingtonlab@gmail.com). Table of Links Abstract & Introduction Methods Results and Discussion Determining Whether Canonicalization Impacts Search Behavior Explanation of Search Behavior & Drawbacks, Future Improvements, and Potential for Misuse Conclusion, Acknowledgements, Author Contributions, & more. Supplementary Figures Abstract & Introduction Abstract & Introduction Methods Methods Results and Discussion Results and Discussion Determining Whether Canonicalization Impacts Search Behavior Determining Whether Canonicalization Impacts Search Behavior Explanation of Search Behavior & Drawbacks, Future Improvements, and Potential for Misuse Explanation of Search Behavior & Drawbacks, Future Improvements, and Potential for Misuse Conclusion, Acknowledgements, Author Contributions, & more. Conclusion, Acknowledgements, Author Contributions, & more. Supplementary Figures Supplementary Figures Supplementary Figures This paper is available on arxiv under CC BY-NC-SA 4.0 DEED license. This paper is available on arxiv under CC BY-NC-SA 4.0 DEED license. available on arxiv

Supplementary Figures for Transformer-Based Chemical Similarity Search

How to Import Icons From Figma in a Cool Way

ምስሎችን ከ Figma አሪፍ በሆነ መንገድ እንዴት ማስመጣት እንደሚቻል

Как да импортирате икони от Figma по страхотен начин

Cómo importar iconos desde Figma de una forma divertida

Kuinka tuoda kuvakkeita Figmasta viileällä tavalla

Figma からアイコンをクールにインポートする方法

Како да увезете икони од Figma на кул начин

Figma-аас дүрсүүдийг хэрхэн гайхалтай аргаар импортлох вэ

Tsela ya go Tsenya Diaekhone Go Tšwa Figma ka Tsela e Fodilego

Figma වෙතින් සිසිල් ආකාරයකින් අයිකන ආනයනය කරන්නේ කෙසේද?

Sida Looga Soo Dejiyo Astaamaha Figma Jidka Qabow

ከመይ ጌርና ካብ ፊግማ ብዝሑል መንገዲ ምልክታት ነእቱ

Cách nhập biểu tượng từ Figma theo cách thú vị

AI-Powered Phishing Scams Are Evolving—Here’s How Businesses Can Fight Back

If you manage a public facing web server, you'll have noticed that bots try their luck on a myriad of non-existing pages. Leverage HAProxy to stop them at the door. Note: The links in this article include affiliate links to Amazon. You won’t be charged anything extra for clicking on these links, but you will be supporting me if you do choose to purchase something through one of these links. Thanks! Your logs are filled with 404 hits on /.DS_Store, /backup.sql, /.vscode/sftp.json and a multitude of other URLs. While these requests are mostly harmless, unless of course, your server actually does have something to offer at those locations, you should placate the bots. Why? Hitting a server is a resource intensive task and, given that those bots have an extensive list of different URLs, there's no caching mechanism that can help you. Besides, stopping bots is always a safety measure. We've previously used HAProxy to mitigate attacks on Wordpress login page, the idea is to extend that approach to also cover 404 errors. Bots will try their best to create havoc in your server I've taken inspiration from Sasa Tekovic, namely on not blocking actual search engine crawlers and allowing 404 on static resources to prevent actual missing resources - an error on your part - from not blocking legitimate users. Before implementing, it's always good to spin up a local test environment. Let's start HAProxy and Apache using Docker. We do need an actual backend server to give us those 404. version : '3'

services:
    haproxy:
        image: haproxy:3.1.3-alpine
        ports:
            - "8100:80"
        volumes:
            - "./haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg"
        networks:
            - webnet
    apache:
        image: httpd:latest
        container_name: apache1
        ports:
            - "8080:80"
        volumes:
            - ./html:/usr/local/apache2/htdocs/
        networks:
            - webnet
            
networks:
    webnet: Then, simply run docker-compose up, and you can access localhost:8100 in your browser. The haproxy.cfg file is pretty much self-explanatory: global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|(google|bing)bot)

    # tracks IPs but exclude hits on static files and search engine crawlers
    http-request track-sc0 src table mock_404_tracking if !static_file !excluded_user_agent
    # increment gpc0 if response code was 404
    http-response sc-inc-gpc0(0) if { status 404 }
   	# checks if the 404 error rate limit was exceeded
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_tracking) ge 5 }

    # whatever backend you're using
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backend to hold a stick table
backend mock_404_tracking
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m) If you get more than 5 hits on 404 requests in a single minute, the bot will be banned for 10 minutes. As it stands, this setup effectively rate-limits bots generating excessive 404s. However, we also want to integrate it with our previous example, where we used HAProxy to block attacks on WordPress. global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	# We may, or may not, be running this with Cloudflare acting as a CDN.
    # If Cloudflare is in front of our servers, user/bot IP will be in 
    # 'CF-Connecting-IP', otherwise user IP with be in 'src'. So we make
    # sure to set a variable 'txn.actual_ip' that has the IP, no matter what
    http-request set-var(txn.actual_ip) hdr_ip(CF-Connecting-IP) if { hdr(CF-Connecting-IP) -m found }
    http-request set-var(txn.actual_ip) src if !{ hdr(CF-Connecting-IP) -m found }

    # gets the actual IP on logs
    log-format "%ci\ %hr\ %ft\ %b/%s\ %Tw/%Tc/%Tt\ %B\ %ts\ %r\ %ST\ %Tr IP:%{+Q}[var(txn.actual_ip)]"

    # common static files where we may get 404 errors and also common search engine
    # crawlers that we don't want blocked
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|google|bing)

    # paths where we will rate limit users to prevent Wordpress abuse
	acl is_wp_login path_end -i /wp-login.php /xmlrpc.php /xmrlpc.php
    acl is_post method POST

	# 404 abuse blocker
    # track IPs but exclude hits on static files and search engine crawlers
    # increment gpc0 counter if response status was 404 and deny if rate exceeded
    http-request track-sc0 var(txn.actual_ip) table mock_404_track if !static_file !excluded_user_agent
    http-response sc-inc-gpc0(0) if { status 404 }
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_track) ge 5 }

    # wordpress abuse blocker
    # track IPs if the request hits one of the monitored paths with a POST request
    # increment gpc1 counter if path was hit and deny if rate exceeded
    http-request track-sc1 var(txn.actual_ip) table mock_wplogin_track if is_wp_login is_post
    http-request sc-inc-gpc1(1) if is_wp_login is_post 
    http-request deny deny_status 403 content-type text/html lf-string "login abuse" if { sc1_gpc1_rate(mock_wplogin_track) ge 5 }
	
    # your backend, here using apache for demonstration purposes
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backends for storing sticky tables
backend mock_404_track
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m)
backend mock_wplogin_track
    stick-table type ip size 100k expire 10m store gpc1,gpc1_rate(1m) Running with two stick tables, and stopping both threats. And there you have it. HAProxy once again used for much more than as a simple reverse proxy. It's a little Swiss Knife! This headlamp has been a game-changer when working on repairs. I had one, but when it broke, hesitated to replace it, resorting to the phone’s flashlight. And sure, it works - but once you experience the convenience of having both hands free again - there’s no going back. If you need reliable, hands-free lighting, this is a must-have! This post was originally posted on https://wasteofserver.com/stop-404-prying-bots-with-haproxy/, you may find newer revisions and additional comments there. If you manage a public facing web server, you'll have noticed that bots try their luck on a myriad of non-existing pages. Leverage HAProxy to stop them at the door. Note: The links in this article include affiliate links to Amazon. You won’t be charged anything extra for clicking on these links, but you will be supporting me if you do choose to purchase something through one of these links. Thanks! Note: The links in this article include affiliate links to Amazon. You won’t be charged anything extra for clicking on these links, but you will be supporting me if you do choose to purchase something through one of these links. Thanks! Your logs are filled with 404 hits on /.DS_Store , /backup.sql , /.vscode/sftp.json and a multitude of other URLs. While these requests are mostly harmless, unless of course, your server actually does have something to offer at those locations, you should placate the bots. /.DS_Store /backup.sql /.vscode/sftp.json Why? Why? Hitting a server is a resource intensive task and, given that those bots have an extensive list of different URLs, there's no caching mechanism that can help you. Besides, stopping bots is always a safety measure. We've previously used HAProxy to mitigate attacks on Wordpress login page , the idea is to extend that approach to also cover 404 errors. mitigate attacks on Wordpress login page Bots will try their best to create havoc in your server I've taken inspiration from Sasa Tekovic , namely on not blocking actual search engine crawlers and allowing 404 on static resources to prevent actual missing resources - an error on your part - from not blocking legitimate users. inspiration from Sasa Tekovic Before implementing, it's always good to spin up a local test environment. Let's start HAProxy and Apache using Docker . We do need an actual backend server to give us those 404 . HAProxy Apache Docker 404 version : '3'

services:
    haproxy:
        image: haproxy:3.1.3-alpine
        ports:
            - "8100:80"
        volumes:
            - "./haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg"
        networks:
            - webnet
    apache:
        image: httpd:latest
        container_name: apache1
        ports:
            - "8080:80"
        volumes:
            - ./html:/usr/local/apache2/htdocs/
        networks:
            - webnet
            
networks:
    webnet: version : '3'

services:
    haproxy:
        image: haproxy:3.1.3-alpine
        ports:
            - "8100:80"
        volumes:
            - "./haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg"
        networks:
            - webnet
    apache:
        image: httpd:latest
        container_name: apache1
        ports:
            - "8080:80"
        volumes:
            - ./html:/usr/local/apache2/htdocs/
        networks:
            - webnet
            
networks:
    webnet: Then, simply run docker-compose up , and you can access localhost:8100 in your browser. docker-compose up localhost:8100 The haproxy.cfg file is pretty much self-explanatory: haproxy.cfg global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|(google|bing)bot)

    # tracks IPs but exclude hits on static files and search engine crawlers
    http-request track-sc0 src table mock_404_tracking if !static_file !excluded_user_agent
    # increment gpc0 if response code was 404
    http-response sc-inc-gpc0(0) if { status 404 }
   	# checks if the 404 error rate limit was exceeded
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_tracking) ge 5 }

    # whatever backend you're using
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backend to hold a stick table
backend mock_404_tracking
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m) global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|(google|bing)bot)

    # tracks IPs but exclude hits on static files and search engine crawlers
    http-request track-sc0 src table mock_404_tracking if !static_file !excluded_user_agent
    # increment gpc0 if response code was 404
    http-response sc-inc-gpc0(0) if { status 404 }
   	# checks if the 404 error rate limit was exceeded
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_tracking) ge 5 }

    # whatever backend you're using
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backend to hold a stick table
backend mock_404_tracking
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m) If you get more than 5 hits on 404 requests in a single minute, the bot will be banned for 10 minutes. As it stands, this setup effectively rate-limits bots generating excessive 404s. However, we also want to integrate it with our previous example, where we used HAProxy to block attacks on WordPress . HAProxy WordPress global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	# We may, or may not, be running this with Cloudflare acting as a CDN.
    # If Cloudflare is in front of our servers, user/bot IP will be in 
    # 'CF-Connecting-IP', otherwise user IP with be in 'src'. So we make
    # sure to set a variable 'txn.actual_ip' that has the IP, no matter what
    http-request set-var(txn.actual_ip) hdr_ip(CF-Connecting-IP) if { hdr(CF-Connecting-IP) -m found }
    http-request set-var(txn.actual_ip) src if !{ hdr(CF-Connecting-IP) -m found }

    # gets the actual IP on logs
    log-format "%ci\ %hr\ %ft\ %b/%s\ %Tw/%Tc/%Tt\ %B\ %ts\ %r\ %ST\ %Tr IP:%{+Q}[var(txn.actual_ip)]"

    # common static files where we may get 404 errors and also common search engine
    # crawlers that we don't want blocked
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|google|bing)

    # paths where we will rate limit users to prevent Wordpress abuse
	acl is_wp_login path_end -i /wp-login.php /xmlrpc.php /xmrlpc.php
    acl is_post method POST

	# 404 abuse blocker
    # track IPs but exclude hits on static files and search engine crawlers
    # increment gpc0 counter if response status was 404 and deny if rate exceeded
    http-request track-sc0 var(txn.actual_ip) table mock_404_track if !static_file !excluded_user_agent
    http-response sc-inc-gpc0(0) if { status 404 }
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_track) ge 5 }

    # wordpress abuse blocker
    # track IPs if the request hits one of the monitored paths with a POST request
    # increment gpc1 counter if path was hit and deny if rate exceeded
    http-request track-sc1 var(txn.actual_ip) table mock_wplogin_track if is_wp_login is_post
    http-request sc-inc-gpc1(1) if is_wp_login is_post 
    http-request deny deny_status 403 content-type text/html lf-string "login abuse" if { sc1_gpc1_rate(mock_wplogin_track) ge 5 }
	
    # your backend, here using apache for demonstration purposes
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backends for storing sticky tables
backend mock_404_track
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m)
backend mock_wplogin_track
    stick-table type ip size 100k expire 10m store gpc1,gpc1_rate(1m) global
    log stdout format raw daemon debug
	
defaults
    log     global
	mode    http

frontend main
    bind *:80
	
	# We may, or may not, be running this with Cloudflare acting as a CDN.
    # If Cloudflare is in front of our servers, user/bot IP will be in 
    # 'CF-Connecting-IP', otherwise user IP with be in 'src'. So we make
    # sure to set a variable 'txn.actual_ip' that has the IP, no matter what
    http-request set-var(txn.actual_ip) hdr_ip(CF-Connecting-IP) if { hdr(CF-Connecting-IP) -m found }
    http-request set-var(txn.actual_ip) src if !{ hdr(CF-Connecting-IP) -m found }

    # gets the actual IP on logs
    log-format "%ci\ %hr\ %ft\ %b/%s\ %Tw/%Tc/%Tt\ %B\ %ts\ %r\ %ST\ %Tr IP:%{+Q}[var(txn.actual_ip)]"

    # common static files where we may get 404 errors and also common search engine
    # crawlers that we don't want blocked
	acl static_file path_end .css .js .jpg .jpeg .gif .ico .png .bmp .webp .csv .ttf .woff .svg .svgz
    acl excluded_user_agent hdr_reg(user-agent) -i (yahoo|yandex|kagi|google|bing)

    # paths where we will rate limit users to prevent Wordpress abuse
	acl is_wp_login path_end -i /wp-login.php /xmlrpc.php /xmrlpc.php
    acl is_post method POST

	# 404 abuse blocker
    # track IPs but exclude hits on static files and search engine crawlers
    # increment gpc0 counter if response status was 404 and deny if rate exceeded
    http-request track-sc0 var(txn.actual_ip) table mock_404_track if !static_file !excluded_user_agent
    http-response sc-inc-gpc0(0) if { status 404 }
    http-request deny deny_status 403 content-type text/html lf-string "404 abuse" if { sc0_gpc0_rate(mock_404_track) ge 5 }

    # wordpress abuse blocker
    # track IPs if the request hits one of the monitored paths with a POST request
    # increment gpc1 counter if path was hit and deny if rate exceeded
    http-request track-sc1 var(txn.actual_ip) table mock_wplogin_track if is_wp_login is_post
    http-request sc-inc-gpc1(1) if is_wp_login is_post 
    http-request deny deny_status 403 content-type text/html lf-string "login abuse" if { sc1_gpc1_rate(mock_wplogin_track) ge 5 }
	
    # your backend, here using apache for demonstration purposes
    use_backend apache_servers

backend apache_servers
    server apache1 apache1:80 maxconn 32

# mock backends for storing sticky tables
backend mock_404_track
    stick-table type ip size 100k expire 10m store gpc0,gpc0_rate(1m)
backend mock_wplogin_track
    stick-table type ip size 100k expire 10m store gpc1,gpc1_rate(1m) Running with two stick tables , and stopping both threats. stick tables And there you have it. HAProxy once again used for much more than as a simple reverse proxy. It's a little Swiss Knife! This headlamp has been a game-changer when working on repairs. I had one, but when it broke, hesitated to replace it, resorting to the phone’s flashlight. And sure, it works - but once you experience the convenience of having both hands free again - there’s no going back. If you need reliable, hands-free lighting, this is a must-have! you experience the convenience of having both hands free again This post was originally posted on https://wasteofserver.com/stop-404-prying-bots-with-haproxy/, you may find newer revisions and additional comments there. This post was originally posted on https://wasteofserver.com/stop-404-prying-bots-with-haproxy/ , you may find newer revisions and additional comments there. https://wasteofserver.com/stop-404-prying-bots-with-haproxy/

Bots Love Wasting Your Server’s Resources—Here’s How to Fight Back

Als bots els encanta malgastar els recursos del vostre servidor: aquí teniu com lluitar

A los bots les encanta desperdiciar los recursos de su servidor: aquí le mostramos cómo contraatacar

Bot-ek zure zerbitzariaren baliabideak xahutzea maite dute: hona hemen nola borrokatu

בוטים אוהבים לבזבז את משאבי השרת שלך - הנה איך להילחם בחזרה

बॉट्स को आपके सर्वर के संसाधनों को बर्बाद करना पसंद है—यहां बताया गया है कि कैसे उनसे लड़ें

ボットはサーバーのリソースを無駄にするのが大好き - 対抗する方法はこれだ

Botiem patīk tērēt jūsu servera resursus — lūk, kā cīnīties

Ботууд серверийнхээ нөөцийг дэмий үрэх дуртай—Үүний эсрэг хэрхэн тэмцэх талаар эндээс үзнэ үү

Bot Suka Membazirkan Sumber Pelayan Anda—Begini Cara Melawan Balik

Boților le place să risipească resursele serverului dvs. — Iată cum să ripostați

බොට්ස් ඔබේ සේවාදායකයේ සම්පත් නාස්ති කිරීමට කැමතියි - ආපසු සටන් කරන්නේ කෙසේද යන්න මෙන්න

Ботови воле да троше ресурсе вашег сервера - ево како да узвратите

BTCS Inc. (Nasdaq: BTCS) (“BTCS” or the “Company”), a leader in blockchain infrastructure and technology, is pleased to announce its partnership with Figment Inc. (“Figment”), one of the world’s foremost blockchain infrastructure providers, for the launch of its Staker Protection Plan. This solution is designed to enhance transaction inclusion and state preservation, addressing a critical pain point for traders and end-users who demand greater certainty for their high-value and time-sensitive transactions. WonderFi Technologies Inc. (TSX: WNDR) (OTCQB: WONDF) (“WonderFi”), a top digital asset company, will join as Figment's first customer in the pilot program. Partnership and Pilot Program Highlights This collaboration underscores BTCS and Figment’s shared commitment to advancing the blockchain ecosystem by addressing critical challenges in wider adoption. With WonderFi’s participation, stakers on the WonderFi-owned Bitbuy and Coinsquare platforms will be the first to enjoy the benefits of the program. The pilot program is anticipated to go live on mainnet in March 2025 in connection with Ethereum’s Pectra update. The Staker Protection Plan program is designed to deliver key benefits, including: Providing end-users with greater confidence that their transactions will be included in a particular block.
Addressing complexities and heightened risks of high-value transactions in cross-chain and cross-venue operations, ensuring timely and predictable trading outcomes.
Optimizing staking rewards rate (SRR) for stakers through improved compliance and performance. Stakers interested in participating in this solution, which is designed to meet applicable regulatory requirements and benefit from increased SRR can contact Figment’s customer success team. End-users seeking information about transaction execution and enhanced features can reach out to the BTCS team for more information. Charles Allen, CEO of BTCS, stated: “By partnering with Figment and integrating WonderFi as the first participant, we are laying a strong foundation for staker empowerment and ecosystem growth. This partnership exemplifies our dedication to delivering solutions that foster revenue growth and operational excellence.” https://www.youtube.com/embed/k3Ct7-XR8kQ Lorien Gabel, CEO of Figment, added: “At Figment, we are committed to driving innovation in blockchain infrastructure to enhance the Ethereum ecosystem and increase adoption. Our partnership with BTCS on this innovative solution demonstrates our dedication to addressing critical challenges in staking operations. By providing solutions that ensure fairness and enhance transaction inclusion, we are fostering a more reliable and fair network for all participants.” Dean Skurka, CEO of WonderFi, stated: “Participating in BTCS’s Staker Protection Plan pilot is a natural extension of our commitment to innovation and growth. We believe that this program will not only enhance our validator operations but also increase revenue for our shareholders and ultimately, higher staking rewards to our customers. We’re excited to be at the forefront of initiatives that have the potential to redefine validator strategies.” About BTCS BTCS Inc. (Nasdaq: BTCS) is a U.S.-based blockchain infrastructure technology company currently focused on driving scalable revenue growth through its Ethereum blockchain infrastructure operations. BTCS has honed its expertise in Ethereum network operations, particularly in block building and validator node management. Its branded block-building operation, Builder+, leverages advanced algorithms to optimize block construction for on-chain validation, thus maximizing gas fee revenues. BTCS also supports other blockchain networks by operating validator nodes and staking its crypto assets across multiple proof-of-stake networks, allowing crypto holders to delegate assets to BTCS-managed nodes. In addition, the Company has developed ChainQ, an AI-powered blockchain data analytics platform, which enhances user access and engagement within the blockchain ecosystem. Committed to innovation and adaptability, BTCS is strategically positioned to expand its blockchain operations and infrastructure beyond Ethereum as the ecosystem evolves. Users can explore how BTCS is revolutionizing blockchain infrastructure in the public markets by visiting www.btcs.com. For more information, users can follow on: Twitter: https://x.com/NasdaqBTCS LinkedIn: https://www.linkedin.com/company/nasdaq-btcs Facebook: https://www.facebook.com/NasdaqBTCS About Figment Figment is the leading provider of staking infrastructure. Figment provides the complete staking solution for over 700 institutional clients and $15B in assets staked across asset managers, exchanges, wallets, foundations, custodians, and banks, to earn rewards on their digital assets. For more information, users can visit www.figment.io. Partnering with BTCS for the Staker Protection Plan exemplifies Figment’s dedication to innovation in the ecosystem and empowerment of stakers. About WonderFi WonderFi is the largest regulated crypto trading platform in Canada and a global leader in centralized and decentralized financial services and products. With over $2.2B in assets under custody, WonderFi is well-positioned to service crypto participants on a global scale with trading, payments, and decentralized products, including purpose-built blockchains and non-custodial wallet applications. Designed to provide investors with diversified investment exposure across the global digital asset ecosystem, the Company has a proven track record of launching new products and obtaining applicable licenses. It is also the owner of market-leading brands, including Bitbuy, Coinsquare, SmartPay and Tetra Trust. As the world continues to move on-chain, WonderFi is strategically placed to capture both market and wallet share through ongoing innovation within the digital asset space. For more information, users can visit www.wonder.fi Forward-Looking Statements Certain statements in this press release constitute “forward-looking statements” within the meaning of the federal securities laws, including statements regarding our anticipated launch on mainnet and revenue growth. Words such as “may,” “might,” “will,” “should,” “believe,” “expect,” “anticipate,” “estimate,” “continue,” “predict,” “forecast,” “project,” “plan,” “intend” or similar expressions, or statements regarding intent, belief, or current expectations, are forward-looking statements. While the Company believes these forward-looking statements are reasonable, undue reliance should not be placed on any such forward-looking statements, which are based on information available to us on the date of this release. These forward-looking statements are based upon assumptions and are subject to various risks and uncertainties, including without limitation regulatory issues, unexpected issues with the Staker Protection Plan and launch as well as issues with Ethereum’s planned Pectra update, as well as risks set forth in the Company’s filings with the Securities and Exchange Commission including its Form 10-K for the year ended December 31, 2023, which was filed on March 21, 2024. Thus, actual results could be materially different. The Company expressly disclaims any obligation to update or alter statements, whether as a result of new information, future events, or otherwise, except as required by law. BTCS Investor Relations: Charles Allen – CEO X (formerly Twitter): @Charles_BTCS Email: ir@btcs.com Figment Contact: Email: marketing@figment.io WonderFi Investor Relations: Charlie Aikenhead Email: Invest@wonder.fi This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here BTCS Inc. (Nasdaq: BTCS ) (“BTCS” or the “Company”), a leader in blockchain infrastructure and technology, is pleased to announce its partnership with Figment Inc. (“Figment”), one of the world’s foremost blockchain infrastructure providers, for the launch of its Staker Protection Plan. BTCS BTCS This solution is designed to enhance transaction inclusion and state preservation, addressing a critical pain point for traders and end-users who demand greater certainty for their high-value and time-sensitive transactions. WonderFi Technologies Inc. (TSX: WNDR) (OTCQB: WONDF) (“WonderFi”), a top digital asset company, will join as Figment's first customer in the pilot program. Partnership and Pilot Program Highlights This collaboration underscores BTCS and Figment’s shared commitment to advancing the blockchain ecosystem by addressing critical challenges in wider adoption. With WonderFi’s participation, stakers on the WonderFi-owned Bitbuy and Coinsquare platforms will be the first to enjoy the benefits of the program. The pilot program is anticipated to go live on mainnet in March 2025 in connection with Ethereum’s Pectra update. The Staker Protection Plan program is designed to deliver key benefits, including: Providing end-users with greater confidence that their transactions will be included in a particular block. Addressing complexities and heightened risks of high-value transactions in cross-chain and cross-venue operations, ensuring timely and predictable trading outcomes. Optimizing staking rewards rate (SRR) for stakers through improved compliance and performance. Providing end-users with greater confidence that their transactions will be included in a particular block. Addressing complexities and heightened risks of high-value transactions in cross-chain and cross-venue operations, ensuring timely and predictable trading outcomes. Optimizing staking rewards rate (SRR) for stakers through improved compliance and performance. Stakers interested in participating in this solution, which is designed to meet applicable regulatory requirements and benefit from increased SRR can contact Figment’s customer success team. End-users seeking information about transaction execution and enhanced features can reach out to the BTCS team for more information. Charles Allen, CEO of BTCS, stated: “By partnering with Figment and integrating WonderFi as the first participant, we are laying a strong foundation for staker empowerment and ecosystem growth. This partnership exemplifies our dedication to delivering solutions that foster revenue growth and operational excellence.” Charles Allen, CEO of BTCS, stated: “By partnering with Figment and integrating WonderFi as the first participant, we are laying a strong foundation for staker empowerment and ecosystem growth. This partnership exemplifies our dedication to delivering solutions that foster revenue growth and operational excellence.” https://www.youtube.com/embed/k3Ct7-XR8kQ https://www.youtube.com/embed/k3Ct7-XR8k Q https://www.youtube.com/embed/k3Ct7-XR8k Lorien Gabel, CEO of Figment, added: “At Figment, we are committed to driving innovation in blockchain infrastructure to enhance the Ethereum ecosystem and increase adoption. Our partnership with BTCS on this innovative solution demonstrates our dedication to addressing critical challenges in staking operations. By providing solutions that ensure fairness and enhance transaction inclusion, we are fostering a more reliable and fair network for all participants.” Lorien Gabel, CEO of Figment, added: “At Figment, we are committed to driving innovation in blockchain infrastructure to enhance the Ethereum ecosystem and increase adoption. Our partnership with BTCS on this innovative solution demonstrates our dedication to addressing critical challenges in staking operations. By providing solutions that ensure fairness and enhance transaction inclusion, we are fostering a more reliable and fair network for all participants.” Dean Skurka, CEO of WonderFi, stated: “Participating in BTCS’s Staker Protection Plan pilot is a natural extension of our commitment to innovation and growth. We believe that this program will not only enhance our validator operations but also increase revenue for our shareholders and ultimately, higher staking rewards to our customers. We’re excited to be at the forefront of initiatives that have the potential to redefine validator strategies.” Dean Skurka, CEO of WonderFi, stated: “Participating in BTCS’s Staker Protection Plan pilot is a natural extension of our commitment to innovation and growth. We believe that this program will not only enhance our validator operations but also increase revenue for our shareholders and ultimately, higher staking rewards to our customers. We’re excited to be at the forefront of initiatives that have the potential to redefine validator strategies.” About BTCS BTCS Inc. (Nasdaq: BTCS) is a U.S.-based blockchain infrastructure technology company currently focused on driving scalable revenue growth through its Ethereum blockchain infrastructure operations. BTCS has honed its expertise in Ethereum network operations, particularly in block building and validator node management. Its branded block-building operation, Builder+, leverages advanced algorithms to optimize block construction for on-chain validation, thus maximizing gas fee revenues. BTCS Inc. BTCS Inc. BTCS also supports other blockchain networks by operating validator nodes and staking its crypto assets across multiple proof-of-stake networks, allowing crypto holders to delegate assets to BTCS-managed nodes. In addition, the Company has developed ChainQ, an AI-powered blockchain data analytics platform, which enhances user access and engagement within the blockchain ecosystem. Committed to innovation and adaptability, BTCS is strategically positioned to expand its blockchain operations and infrastructure beyond Ethereum as the ecosystem evolves. Users can explore how BTCS is revolutionizing blockchain infrastructure in the public markets by visiting www.btcs.com . For more information, users can follow on: www.btcs.com www.btcs.com Twitter: https://x.com/NasdaqBTCS https://x.com/NasdaqBTCS https://x.com/NasdaqBTCS LinkedIn: https://www.linkedin.com/company/nasdaq-btcs https://www.linkedin.com/company/nasdaq-btcs https://www.linkedin.com/company/nasdaq-btcs Facebook: https://www.facebook.com/NasdaqBTCS https://www.facebook.com/NasdaqBTCS https://www.facebook.com/NasdaqBTCS About Figment Figment is the leading provider of staking infrastructure. Figment provides the complete staking solution for over 700 institutional clients and $15B in assets staked across asset managers, exchanges, wallets, foundations, custodians, and banks, to earn rewards on their digital assets. For more information, users can visit www.figment.io . Partnering with BTCS for the Staker Protection Plan exemplifies Figment’s dedication to innovation in the ecosystem and empowerment of stakers. Figment Figment www.figment.io www.figment.io About WonderFi WonderFi is the largest regulated crypto trading platform in Canada and a global leader in centralized and decentralized financial services and products. With over $2.2B in assets under custody, WonderFi is well-positioned to service crypto participants on a global scale with trading, payments, and decentralized products, including purpose-built blockchains and non-custodial wallet applications. WonderFi WonderFi Designed to provide investors with diversified investment exposure across the global digital asset ecosystem, the Company has a proven track record of launching new products and obtaining applicable licenses. It is also the owner of market-leading brands, including Bitbuy, Coinsquare, SmartPay and Tetra Trust. As the world continues to move on-chain, WonderFi is strategically placed to capture both market and wallet share through ongoing innovation within the digital asset space. For more information, users can visit www.wonder.fi www.wonder.fi www.wonder.fi Forward-Looking Statements Certain statements in this press release constitute “forward-looking statements” within the meaning of the federal securities laws, including statements regarding our anticipated launch on mainnet and revenue growth. Words such as “may,” “might,” “will,” “should,” “believe,” “expect,” “anticipate,” “estimate,” “continue,” “predict,” “forecast,” “project,” “plan,” “intend” or similar expressions, or statements regarding intent, belief, or current expectations, are forward-looking statements. While the Company believes these forward-looking statements are reasonable, undue reliance should not be placed on any such forward-looking statements, which are based on information available to us on the date of this release. These forward-looking statements are based upon assumptions and are subject to various risks and uncertainties, including without limitation regulatory issues, unexpected issues with the Staker Protection Plan and launch as well as issues with Ethereum’s planned Pectra update, as well as risks set forth in the Company’s filings with the Securities and Exchange Commission including its Form 10-K for the year ended December 31, 2023, which was filed on March 21, 2024. Thus, actual results could be materially different. The Company expressly disclaims any obligation to update or alter statements, whether as a result of new information, future events, or otherwise, except as required by law. BTCS Investor Relations: Charles Allen – CEO X (formerly Twitter): @Charles_BTCS @Charles_BTCS @Charles_BTCS Email: ir@btcs.com ir@btcs.com ir@btcs.com Figment Contact: Email: marketing@figment.io marketing@figment.io marketing@figment.io WonderFi Investor Relations: Charlie Aikenhead Email: Invest@wonder.fi Email: Invest@wonder.fi Invest@wonder.fi Invest@wonder.fi This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

BTCS Unveils Strategic Partnership With Figment And WonderFi Leading Its Staker Protection Plan

BTCS раскрывае стратэгічнае партнёрства з Figment і WonderFi, якія ўзначальваюць план абароны стакераў

BTCS otkriva strateško partnerstvo sa Figmentom i WonderFi-jem koji predvode svoj plan zaštite stekera

Το BTCS αποκαλύπτει τη στρατηγική συνεργασία με το Figment και το WonderFi να ηγείται του σχεδίου προστασίας Staker

BTCS revela una asociación estratégica con Figment y WonderFi para liderar su plan de protección de los participantes

BTCS presenta unha asociación estratéxica con Figment e WonderFi que lideran o seu plan de protección de staker

BTCS חושפת שותפות אסטרטגית עם Figment ו-WonderFi שמובילים את תוכנית ההגנה על המעריצים שלה

बीटीसीएस ने फिगमेंट और वंडरफाई के साथ रणनीतिक साझेदारी का खुलासा किया, जो इसके स्टेकर प्रोटेक्शन प्लान का नेतृत्व करेगा

BTCS、ステーカー保護計画を主導するFigmentおよびWonderFiとの戦略的パートナーシップを発表

BTCS ເປີດເຜີຍການຮ່ວມມືຍຸດທະສາດກັບ Figment ແລະ WonderFi ນໍາພາແຜນການປົກປ້ອງ Staker ຂອງຕົນ

BTCS ले आफ्नो स्टेकर सुरक्षा योजनाको नेतृत्व गर्दै फिगमेन्ट र वन्डरफाइसँग रणनीतिक साझेदारीको अनावरण गर्‍यो

BTCS e Utolla Selekane sa Togamaano Le Figment Le WonderFi e Eteletšego Pele Leano la Yona la Tšhireletšo ya Batšeakarolo

BTCS Yashyize ahagaragara Ubufatanye Bw’ibishushanyo na WonderFi Biyobora Gahunda Yayo yo Kurinda

Today, Figment, the leading independent staking infrastructure provider with over $15B in staked assets, announced it is joining the Blockchain Association, the leading trade association for the cryptocurrency industry in the United States. Joining forces with the country’s preeminent exchanges, venture capital firms, infrastructure, and service providers emphasizes Figment’s continued leadership role in shaping regulation that facilitates institutional crypto adoption. As institutional interest in protocol staking continues to grow, Figment's membership in the Blockchain Association reinforces its commitment to working with policymakers and regulators to establish clear guidelines for the staking ecosystem in particular. This collaboration comes at a crucial time as the industry seeks regulatory clarity, particularly regarding the treatment of protocol staking in exchange-traded products. "We are excited to welcome Figment as a member of the Blockchain Association. As the U.S. moves into a new era for digital assets, establishing regulatory clarity around staking will be critical. We look forward to the Figment team lending their expertise to these policy conversations in DC”, states Kristin Smith, CEO at Blockchain Association. Through the Association, Figment will focus on key educational and advocacy initiatives, including: Protocol staking in ETPs
Development of staking regulatory frameworks
Education on the distinction between protocol staking and yield products
Cross-jurisdictional policy alignment As a member of the Blockchain Association, Figment strengthens its position as a trusted voice in shaping the future of digital asset infrastructure. This membership enhances the company's ability to serve its 700+ institutional clients while contributing to the development of responsible industry standards. Figment continues to educate American policymakers on staking’s critical importance in securing and decentralizing Proof-of-Stake (PoS) networks. Having reached a $633 billion market cap, PoS networks are noteworthy for offering a more sustainable alternative to energy-intensive Proof-of-Work mining. The approval of Ethereum in ETFs in May 2024 marked another significant milestone for Proof-of-Stake networks. The entire Figment team is energized to bring its staking expertise to the Blockchain Association’s agenda at this critical moment for the future of the nation’s crypto policy. Beyond navigating the hopeful addition of staking to ETPs, Figment is also helping traditional banks and brokerages navigate the opportunities of staking within regulated financial institutions made possible through SAB 122. “Protocol staking is the backbone of blockchain security, ensuring network integrity and decentralization,” adds Jennie Levin, Chief Regulatory & Strategy Officer. “Figment is thrilled to join the Blockchain Association, to align with industry leaders to further this message and advocate for a thriving, secure, and decentralized future.” About Blockchain Association The Blockchain Association is the unified voice of the cryptocurrency industry. Their members include the sector’s leading investors, companies, projects, and protocols, working together to support a future-forward, pro-innovation national policy and regulatory framework for the crypto economy. For more information, users can visit the blockchainassociation.org. About Figment Figment is the leading provider of staking infrastructure. Figment provides the complete staking solution for over 700 institutional clients, including asset managers, exchanges, wallets, foundations, custodians, and large token holders, to earn rewards on their digital assets. On Ethereum, Figment is the largest non-custodial staking provider of staked ETH. Institutional staking services from Figment include seamless point-and-click staking, portfolio reward tracking, API integrations, audited infrastructure, and slashing protection. To learn more about Figment, users can visit figment.io. This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here Today, Figment, the leading independent staking infrastructure provider with over $15B in staked assets, announced it is joining the Blockchain Association , the leading trade association for the cryptocurrency industry in the United States. Blockchain Association Blockchain Association Joining forces with the country’s preeminent exchanges, venture capital firms, infrastructure, and service providers emphasizes Figment’s continued leadership role in shaping regulation that facilitates institutional crypto adoption. As institutional interest in protocol staking continues to grow, Figment's membership in the Blockchain Association reinforces its commitment to working with policymakers and regulators to establish clear guidelines for the staking ecosystem in particular. This collaboration comes at a crucial time as the industry seeks regulatory clarity, particularly regarding the treatment of protocol staking in exchange-traded products. "We are excited to welcome Figment as a member of the Blockchain Association. As the U.S. moves into a new era for digital assets, establishing regulatory clarity around staking will be critical. We look forward to the Figment team lending their expertise to these policy conversations in DC”, states Kristin Smith, CEO at Blockchain Association. "We are excited to welcome Figment as a member of the Blockchain Association. As the U.S. moves into a new era for digital assets, establishing regulatory clarity around staking will be critical. We look forward to the Figment team lending their expertise to these policy conversations in DC”, states Kristin Smith, CEO at Blockchain Association. Through the Association, Figment will focus on key educational and advocacy initiatives, including: Protocol staking in ETPs Development of staking regulatory frameworks Education on the distinction between protocol staking and yield products Cross-jurisdictional policy alignment Protocol staking in ETPs Development of staking regulatory frameworks Education on the distinction between protocol staking and yield products Cross-jurisdictional policy alignment As a member of the Blockchain Association, Figment strengthens its position as a trusted voice in shaping the future of digital asset infrastructure. This membership enhances the company's ability to serve its 700+ institutional clients while contributing to the development of responsible industry standards. Figment continues to educate American policymakers on staking’s critical importance in securing and decentralizing Proof-of-Stake (PoS) networks. Having reached a $633 billion market cap , PoS networks are noteworthy for offering a more sustainable alternative to energy-intensive Proof-of-Work mining. $633 billion market cap $633 billion market cap The approval of Ethereum in ETFs in May 2024 marked another significant milestone for Proof-of-Stake networks. approval of Ethereum in ETFs in May 2024 approval of Ethereum in ETFs in May 2024 The entire Figment team is energized to bring its staking expertise to the Blockchain Association’s agenda at this critical moment for the future of the nation’s crypto policy. Beyond navigating the hopeful addition of staking to ETPs, Figment is also helping traditional banks and brokerages navigate the opportunities of staking within regulated financial institutions made possible through SAB 122 . SAB 122 SAB 122 “Protocol staking is the backbone of blockchain security, ensuring network integrity and decentralization,” adds Jennie Levin, Chief Regulatory & Strategy Officer. “Figment is thrilled to join the Blockchain Association, to align with industry leaders to further this message and advocate for a thriving, secure, and decentralized future.” “Protocol staking is the backbone of blockchain security, ensuring network integrity and decentralization,” adds Jennie Levin, Chief Regulatory & Strategy Officer. “Figment is thrilled to join the Blockchain Association, to align with industry leaders to further this message and advocate for a thriving, secure, and decentralized future.” About Blockchain Association The Blockchain Association is the unified voice of the cryptocurrency industry. Their members include the sector’s leading investors, companies, projects, and protocols, working together to support a future-forward, pro-innovation national policy and regulatory framework for the crypto economy. For more information, users can visit the blockchainassociation.org . The Blockchain Association The Blockchain Association the blockchainassociation.org the blockchainassociation.org About Figment Figment is the leading provider of staking infrastructure. Figment provides the complete staking solution for over 700 institutional clients, including asset managers, exchanges, wallets, foundations, custodians, and large token holders, to earn rewards on their digital assets. Figment Figment On Ethereum, Figment is the largest non-custodial staking provider of staked ETH. Institutional staking services from Figment include seamless point-and-click staking, portfolio reward tracking, API integrations, audited infrastructure, and slashing protection. To learn more about Figment, users can visit figment.io . figment.io figment.io This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here here here

Figment Joins Blockchain Association To Advance U.S. Crypto Policy And Staking Adoption

Figment далучаецца да Blockchain Association для прасоўвання крыптапалітыкі ЗША і прыняцця ставак

Figment se une a la Blockchain Association para promover la adopción de políticas criptográficas y staking en EE. UU.

Figment si unisce alla Blockchain Association per promuovere la politica statunitense sulle criptovalute e l'adozione dello staking

フィグメント、米国の暗号通貨政策とステーキング導入を推進するためブロックチェーン協会に加盟

Figment се приклучува на асоцијацијата на блокчејн за да ја унапреди американската политика за крипто и усвојувањето на удели

Figment Menyertai Persatuan Blockchain Untuk Memajukan Dasar Kripto A.S. dan Penerimaan Staking

فګمینټ د بلاکچین ټولنې سره یوځای کیږي ترڅو د متحده ایالاتو د کریپټو پالیسۍ او سټیکینګ اختیار ته وده ورکړي

Igishushanyo Cyinjiye mu Ishyirahamwe rya Blockchain Gutezimbere Politiki yo muri Amerika Crypto no Kwakira

Figment bashkohet me Shoqatën Blockchain për të avancuar politikën e kriptove në SHBA dhe miratimin e aksioneve

Figment Inajiunga na Chama cha Blockchain Ili Kuendeleza Sera ya U.S. Crypto na Kupitishwa kwa Staking

Figment ABŞ-nyň kripto syýasatyny öňe sürmek we ogullyga almak üçin Blokçain birleşigine goşulýar

Figment AQShning kripto siyosatini va stakingni qabul qilishni rivojlantirish uchun Blockchain assotsiatsiyasiga qo'shildi

Flo Design System with Figma as a Source

Here's a shocking number to start your day: Americans received over 70 billion robocalls in 2024. That's about 211 calls per person. As someone who writes about AI and digital strategy, I never thought I'd be sharing anti-spam tactics, but here we are – because this problem is too big to ignore. The Scale of the Problem Is Staggering Let's put this in perspective. While Americans were drowning in robocalls, Canadians faced 6+ billion spam calls. Scammers didn't just waste our time – they walked away with $10 billion from North American victims alone. Globally? The Global Anti-Scam Alliance (GASA) reported a mind-numbing $1.03 trillion lost to scams in 2024. What makes this worse is that modern scams are evolving faster than traditional defenses. Thanks to record numbers of data breaches, AI and automation, these aren't your grandmother's obvious spam calls anymore. But here's the good news: we can fight fire with fire. Four Innovative Tools to Fight Back After testing dozens of solutions, here are the four most effective tools I've found that actually work – and some even make fighting back fun. 1. Jolly Roger Telephone Company ($1.99/month) Think of Jolly Roger as your personal army of chatbots designed to waste scammers' time. Their AI-powered bots keep scammers talking in hilarious ways while you get on with your day. After nine years in the business, they've mastered the art of scammer-baiting. https://youtu.be/9ox6rnPD1ko?embedable=true Pro Tip: Record and save your favorite bot conversations. They make great educational material for teaching others about scam tactics. 2. Re: Scam (Free) Here's a brilliant idea: forward your spam emails to me@rescam.org, and their AI bot will engage scammers in endless email chains. It's like having a tireless assistant whose only job is to frustrate scammers. The impact? Over 45,000 replies were sent and nearly 3,700 hours of scammers' time was wasted. Power Move: Create a filter in your email to automatically forward suspected scam emails to Re:Scam while moving them to trash in your inbox. Check out their website for more info here. Daisy by O2 (Free) https://youtu.be/RV_SdCfZ-0s?embedable=true Daisy is the sweet-sounding AI grandmother scammers who wish they never called. While you can't subscribe to Daisy directly, you can report scam numbers to 7726 (spells "SPAM"). The service then uses tools being Daisy to investigate and combat these scammers. Quick Tip: Save 7726 in your contacts as "Report SPAM" for easy access. You’ll get a confirmation text back if you’ve sent it correctly. RoboKiller ($3.99/month) https://youtu.be/ccs-4OWr9a8?embedable=true Another veteran of the group, RoboKiller has spent seven years perfecting spam defense. Beyond just blocking calls and texts, it lets you customize AI responses to mess with scammers. Think of it as building your personal spam firewall with a sense of humor. Why This Matters More Than Ever We're not just fighting annoying interruptions – we're protecting our mental space and financial security. Every minute a scammer spends talking to a bot is a minute they're not spending targeting vulnerable people. Taking Action: Your Next Steps Choose at least one tool from this list to implement today.


Save the spam reporting number (7726) in your contacts.


Set up email filters to automatically handle suspected scam emails.


Share these tools with at least three people you care about The Bottom Line You don't have to be a tech expert to fight back against scammers. Whether you choose the free options or invest in paid tools, taking action is better than remaining vulnerable. The best part? You might even have some fun while making the digital world a little safer for everyone. Found this guide helpful? Share it with friends and family – because the best way to fight scammers is to make their tactics known and their targets harder to reach. Have a product or app you enjoy for combatting scams and spam? Tell us about it in the comments! OTHER POPULAR RECENT ARTICLES BY THE AUTHOR https://hackernoon.com/30-growth-hacking-examples-to-accelerate-your-business?embedable=true https://hackernoon.com/future-proof-your-marketing-with-this-guide-on-writing-for-ai-search-engines?embedable=true https://hackernoon.com/the-2024-social-media-algorithm-update-explained?embedable=true Here's a shocking number to start your day: Americans received over 70 billion robocalls in 2024. That's about 211 calls per person. As someone who writes about AI and digital strategy, I never thought I'd be sharing anti-spam tactics, but here we are – because this problem is too big to ignore. The Scale of the Problem Is Staggering Let's put this in perspective. While Americans were drowning in robocalls, Canadians faced 6+ billion spam calls. Scammers didn't just waste our time – they walked away with $10 billion from North American victims alone. Globally? The Global Anti-Scam Alliance (GASA) reported a mind-numbing $1.03 trillion lost to scams in 2024 . $1.03 trillion lost to scams in 2024 What makes this worse is that modern scams are evolving faster than traditional defenses. Thanks to record numbers of data breaches , AI and automation, these aren't your grandmother's obvious spam calls anymore. But here's the good news: we can fight fire with fire. record numbers of data breaches Four Innovative Tools to Fight Back After testing dozens of solutions, here are the four most effective tools I've found that actually work – and some even make fighting back fun. 1. Jolly Roger Telephone Company ($1.99/month) Think of Jolly Roger as your personal army of chatbots designed to waste scammers' time. Their AI-powered bots keep scammers talking in hilarious ways while you get on with your day. After nine years in the business, they've mastered the art of scammer-baiting. https://youtu.be/9ox6rnPD1ko?embedable=true https://youtu.be/9ox6rnPD1ko?embedable=true Pro Tip: Record and save your favorite bot conversations. They make great educational material for teaching others about scam tactics. Pro Tip: 2. Re: Scam (Free) Here's a brilliant idea: forward your spam emails to me@rescam.org , and their AI bot will engage scammers in endless email chains. It's like having a tireless assistant whose only job is to frustrate scammers. The impact? Over 45,000 replies were sent and nearly 3,700 hours of scammers' time was wasted. me@rescam.org Power Move: Create a filter in your email to automatically forward suspected scam emails to Re:Scam while moving them to trash in your inbox. Power Move: Check out their website for more info here . here Daisy by O2 (Free) https://youtu.be/RV_SdCfZ-0s?embedable=true https://youtu.be/RV_SdCfZ-0s?embedable=true Daisy is the sweet-sounding AI grandmother scammers who wish they never called. While you can't subscribe to Daisy directly, you can report scam numbers to 7726 (spells "SPAM"). The service then uses tools being Daisy to investigate and combat these scammers. Quick Tip: Save 7726 in your contacts as "Report SPAM" for easy access. You’ll get a confirmation text back if you’ve sent it correctly. Quick Tip: RoboKiller ($3.99/month) https://youtu.be/ccs-4OWr9a8?embedable=true https://youtu.be/ccs-4OWr9a8?embedable=true Another veteran of the group, RoboKiller has spent seven years perfecting spam defense. Beyond just blocking calls and texts, it lets you customize AI responses to mess with scammers. Think of it as building your personal spam firewall with a sense of humor. Why This Matters More Than Ever We're not just fighting annoying interruptions – we're protecting our mental space and financial security. Every minute a scammer spends talking to a bot is a minute they're not spending targeting vulnerable people. Taking Action: Your Next Steps Choose at least one tool from this list to implement today. Save the spam reporting number (7726) in your contacts. Set up email filters to automatically handle suspected scam emails. Share these tools with at least three people you care about Choose at least one tool from this list to implement today. Choose at least one tool from this list to implement today. Save the spam reporting number (7726) in your contacts. Save the spam reporting number (7726) in your contacts. Set up email filters to automatically handle suspected scam emails. Set up email filters to automatically handle suspected scam emails. Share these tools with at least three people you care about Share these tools with at least three people you care about The Bottom Line You don't have to be a tech expert to fight back against scammers. Whether you choose the free options or invest in paid tools, taking action is better than remaining vulnerable. The best part? You might even have some fun while making the digital world a little safer for everyone. Found this guide helpful? Share it with friends and family – because the best way to fight scammers is to make their tactics known and their targets harder to reach. Found this guide helpful? Share it with friends and family – because the best way to fight scammers is to make their tactics known and their targets harder to reach. Have a product or app you enjoy for combatting scams and spam? Tell us about it in the comments! OTHER POPULAR RECENT ARTICLES BY THE AUTHOR OTHER POPULAR RECENT ARTICLES BY THE AUTHOR https://hackernoon.com/30-growth-hacking-examples-to-accelerate-your-business?embedable=true https://hackernoon.com/30-growth-hacking-examples-to-accelerate-your-business?embedable=true https://hackernoon.com/future-proof-your-marketing-with-this-guide-on-writing-for-ai-search-engines?embedable=true https://hackernoon.com/future-proof-your-marketing-with-this-guide-on-writing-for-ai-search-engines?embedable=true https://hackernoon.com/the-2024-social-media-algorithm-update-explained?embedable=true https://hackernoon.com/the-2024-social-media-algorithm-update-explained?embedable=true

The Ultimate Tech Guide to Fighting Spam and Scams in 2025: How to Turn the Tables on Scammers

FIG

withfig.com

-- employees

Since n.d.

COMPANY RANKING

FIG

EVERGREEN INDEX #5433

Representing this company? Click here to claim and customize this page!

Fig WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

FIG